Need an etc/1password/custom_allowed_browsers equivalent on Android

I use a custom ROM on android that uses a more secure and private fork of Chromium (Cromite). There are many such forks and it would be unreasonable to expect 1Password to explicitly support all of them. However, since they are functionally identical to Chrome, all "support" would entail would be to allow users to append to the hardcoded whitelist of browsers as is already allowed in Linux.

In recent years with the increasing adoption of passkeys, this has gone from a major inconvenience to a serious blocker to fundamental 1Password functionality---since I cannot use the built-in OS autofill suggestion for passkeys as I can for passwords, I am altogether unable to use passkeys on Android.

What is so frustrating is that over the years many people have already brought this issue to 1Password, and it would be be trivial to fix (I could write a patch myself if I had access to the client's source code). 1Password is still the best password manager I have used, and if you do not allow me to use it I will be very sad to switch to Bitwarden.