Not a rhetorical question: When is the last time you’ve visited a non-HTTPs website?
> you wont be part of a traffic redirection network
These are also only a concern for HTTP.
Other common use cases for VPNs include geo-unblocking, and hosting IP ranges are commonly blocked by streaming sites.
I can’t think of a good reason to use a VPS for a VPN anymore these days, to be honest – the privacy/security landscape has changed dramatically over the last few years.
You probably get better privacy these days on public (free/unauthenticated) Wi-Fi than you would on many "free" or paid VPN services.
Need to bypass geoblocking, e.g. when traveling? You'll likely need a residential IP -> use your own network at home (e.g. Tailscale or a self-setup solution) or one of the shady "residential IP broker" utilizing commercial VPNs out there.
Want privacy (from visited sites' trackers)? Your VPS is definitely not that: The IP is static, and if you send your entire traffic through it, this is much more fingerprintable than even residential web usage. -> Use a commercial VPN that you can trust (I don't know many) or something like iCloud Private Relay or TOR.
Want privacy from your ISP tracking you (including public Wi-Fis), and only that? Then, yes, a VPS-based VPN might be for you (or any of the commercial VPNs out there).
But my claim is that the last one (and only that) is probably not the biggest concern of most people.
I’ve run a private vpn for extended family off of my residential connection for this reason. It helps them and me.
On another note, one of the first firewall rules that many of my clients ask for is to block cloud servers IP ranges.
Installing open VPN is like carrying the One Ring to Mount Doom. I’ve installed operating systems, databases, web servers, full LAMP stacks that took less effort.