well that's interesting - vanadium (and other apps I installed) happily connected to the non-tunneled net while my main-profile was in always-on/block-without mode - but it appears my VPN app would not. VPN cloned to work profile timed out on login, until I disabled the main profile VPN.
Backing up: as part of triaging this, I had attempted to install protonvpn in the work profile, but logging in just hung; I assumed (given the behavior of other apps), I assume this was just confirmation you couldn't have "second" vpn. However, poking around I tried again, disabling always-on/block-without first ... and I was able to log in & setup VPN in the work profile. Then re-enable always-on/block without in the main profile. And now apps report the IP's I'd expect in both main & work.
Has something changed here? In an effort to narrow the post to my problem, I left out what prompted this - my work profile, which has been working as I'd expect for over a year, stopped having net connectivity recently (within the last month or so?) I don't use it a ton so just ignore it, but finally sat down to fix it here. I don't recall ever setting up VPN there. Triaging that, I noticed that the work apps connected fine when I turned off always-on/block-without in my main profile's VPN.
None of this is making 100% sense to me. How is VPN + work profile supposed to work? And if you're intended to have two VPN's running (main + work), which is just fine - did something change in recent android updates here?