[zer0tonin]

Those two are pretty big already to be honest. I guess a third one would be avoiding eavesdropping on public wi-fis.

[justapassenger]

With TLS being everywhere, and just few clicks away from having DNS over TLS, I really don't get eavesdropping on public wifi prop value.

[michaelt]

1. example.com is not on the HSTS preload list

2. Because you normally visit example.com using an incognito window, your browser hasn't cached the redirect to SSL, or the address bar suggestion, and you haven't bookmarked the site.

3. You key in example.com, the browser connects over http, and the evil wifi MITMs your unencrypted connection - removing the redirect to SSL and messing with the page however the evildoer wants.

Obviously a VPN provider can also do this, but you might hope they're less likely to.

[numpad0]

VPN unifies all destination IPs to server.ip.addr.ess. IP reverse lookups tells some stories if you are to be so paranoid

[TZubiri]

Additionally, if ConsumerVPNs provide encryption, don't they provide encryption from the stretch between the consumer to the proxy? The stretch between the proxy to the destination would not have additional encryption, and there is no reason to believe that the second transit would be shorter.

[octo888]

TLS doesn't hide which websites (hostnames) you visit