firefox > about:preferences > Network Settings (at bottom) > Manual proxy configuration > SOCKS v5 (enter details and your password if you set it up in bitvise) > also check "Proxy DNS when using SOCKS v5" at bottom
Does Firefox route WebRTC through a socks proxy? Does it leak your locally configured IP when WebRTC is initiated?
Even if the specific case of Firefox can be configured correctly and you have the source to verify that's it only sending traffic over the socks proxy, manually configuring every app to use a socks proxy is brittle and error pone, and for some apps just won't work.
Much more straightforward to just have a system wide VPN as the only available route for outbound traffic so that all apps use it transparently.
Calm down. If you're down the road about privacy, and you didn't already know about the webRTC thing, I don't know what to tell you. Do you want me to hold your hand and pretend you're my grandma, or are you a smart HN commenter? Seven proxies won't hide your IP if it's leaked by design implementation, and you have it enabled in a layer above the session layer. Hence why I prefer to assume a system is compromised and ONLY trust the apps I have verified and validated... If I'm doing something that needs that. "Whole-system" vpns are naieve. You're just looking to blame people.
When you get down from your horse, go and learn the Greenhills kernel and why everything from the nsa to the f35 uses it.
jfc dude it was just pointed out that the ssh+socks thing you provided has issues and there are simpler solutions. Ofc it depends on your goals but yeah if you care about privacy its a terrible solution because its incredibly brittle and there are much easier ways like using that ssh connection to setup a wireguard tunnel with a one-liner or any number of other more comprehensive solutions. Don't take it so personally, if it works for you it works for you.