Seems okay-ish if it removes all the AI slop and spam quickly. The mods already have the technical power to dictate things, so this rule change just make their actions tie more closely to their management reputation

Building a new way does not adequately means giving up on developer verification. In the last paragraph, Google is also promoting the verification for non-GPlay developers.

Out of all possibilities in this universe, there may be a chance that these new flows include user verification instead of developer.

There should also be a rule to rephrase "sideloading" as "installing from non-Google-approved sources" at this point.

What would you say is a good on-device filtering solution? I guess this would require locally MITM the TLS stuff does it?

Something like uBO for outside the browser would be nice

If you have the WireGuard config from Mullvad already, just edit your wg.conf files on client devices to route all traffic via the Mullvad servers. Basically replace all the values of the [Peer] block with Mullvad values.

If you can share your Mullvad wg config file and your wireguard-server config file here, we can sort this out together

Edit: actually since your only goal is to increase the Mullvad device limits, why not just use Mullvad-provided confs directly in your client WireGuard apps? Should be straightforward to do