EDIT to clarify because i feel many might not be aware how easy it is: 1) enable port forwarding in your sshd config (implies you can't just do this on a server which you don't admin and which has this disabled) 2) point bitvise's socks5 proxy server feature at the ssh server 3) point anything that needs to be tunneled at the bitvise client's port (default 1080) e.g. firefox. 4) voila, packets leave and return via the ssh server's public IP.
there you go with an easy socks5 proxy.
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.
also, this sounds like fud.
so not fud, it's a more brittle way to do it.
Therefore I don't think this is fud for the wider privacy case.
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.