I think a browser extension would only route through the VPN for traffic within that browser.

It’s easy to test - with the extension running, check your IP in two browsers (or, better yet, from the terminal)

I have a feeling you're on to something, but also feel this might be needed for a niche use case.

And like another comment pointed out, in-browser extensions obviously only impact the browser. But like you said you'll be using it to prevent sites from knowing you're using tor so that should be alright.

I like this idea for using "free" or suspicious VPNs. But all this routing would totally slow down the connection, especially on the already limited free vpn connections.

First off, I would be careful around browser-based VPNs, especially free ones. If it’s in the browser it’s often just a proxy (as opposed to wireguard or openvpn), which is potentially bad for normal functionality or privacy. Also, if it’s a free service then it almost certainly collects your data itself, and won’t necessarily be allowed by sites either.

That being said, there are two ways to layer the two type of tunnels:

Connecting to the VPN first is relatively common. This means that your ISP can’t see you connecting to Tor. Furthermore, VPNs are designed to tunnel your entire system, while Tor generally is not. Thus, you can have some traffic that is merely VPN protected and some that runs through the Tor network as well. In this situation my ISP knows which VPN provider I use, my VPN provider knows (1) my identity and (2) my network activity outside of Tor, and sites that I visit can only see that I use Tor.

The other direction is to connect first to Tor, and tunnel the VPN connection through there. This is very much not intended: Tor only tunnels TCP, while most VPN protocols use UDP (only, or more efficiently). The reason is that it’s actually quite difficult to hide your identity from your VPN provider. If the VPN is the innermost tunnel, then that means that it has access to all your network traffic. I’ll assume that all of it is encrypted with TLS (but be careful because a single error is bad). Then, the VPN only knows which domains you visit, how long, how much data, and at what times. This is still quite significant. Then there’s the issue of payment. If you choose a free service, it almost certainly means it’s selling your data. I will say that this is better than most other uses for free VPNs, but it’s still pretty sketchy. If you’re paying, then you need one which accepts payments in monero (or zcash or another private cryptocurrency) or cash by mail.

Overall, Tor over VPN is relatively normal. I use this configuration regularly. VPN over Tor is highly unusual, and you should consider if you need it. If you need a recommendation for a VPN though, Mullvad supports both monero and cash by mail (sweden), and is generally a good all around VPN (as long as you don’t need port forwarding). One final thing to note: If for some reason you want to use a VPN on both sides, do not use the same VPN, even with separate accounts. Probably, they won’t check, but at that point you might as well just use straight Mullvad VPN.

I feel like you’d need to use this in like, a Whonix VM to be confident no UDP packets are leaking and no hardware/OS info gathered by the presumably malicious browser extension.