vividsquirrel What I think nobody would really be upset by is disabling the carrier's WiFi connection when WiFi Calling is disabled since it has no reason to connect.
That might reduce surprise... but the name "Wi-Fi calling" includes calling as part of the name. It's not called "Wi-Fi calling and text messages and voicemail alerts". Meanwhile, again, there is already a toggle that disables all calling and text messages and voicemail alerts for a given carrier account. The desired effect can already be accomplished, at the cost of a few extra taps.
vividsquirrel It seems there are github issues about this but they appear to be pretty old and/or pretty dead, for example [#887](https:///github.com/GrapheneOS/os-issue-tracker/issues/887).
There has been a lot of water under the bridge since then. For example, several changes by Google have made it much harder to keep up with AOSP. A feature that might have been "interesting but not urgent" in 2022 might be somewhat reduced in priority in 2025.
If it's easy to fork that repository and bring it up to date with A16 QPR1 that might increase the interest of the developers in reviewing and then perhaps testing and maintaining the code. I would point out that this seems to me much less critical than VoLTE forcing, and that had been stalled for a while, until it became an urgent need for a large number of users.