NB. I actually do not encrypt then re-encrypt for the majority of HTTP requests I make

I generate HTTP myself using own programs and connect to the localhost proxy using various TCP clients. The proxy does the encryption and remote connections not the client programs

I process response bodies, using own software, into SQL, CSV, simple HTML or plain text

I'm not using a graphical web browser to make HTTP requests

This design isn't for everybody, but it's what I strongly prefer

As such, in the way I use it, for the majority of HTTP traffic, no speed is sacrificed

There are a variety of proxies that can be used to forward traffic. I use only a small selection. The largest one I use is haproxy, the smallest one I use is tinyproxy. Personal preference will vary

The local DNS setup is just habit. I have been using djbdns and a custom root.zone for a very long time, before "privacy" was the issue it is today, and I have own particular prefetences. Every user is different. Using a firewall to send traffic to the proxy is an alternative

The motivation for me was always experimentation, learning and control, not "privacy"

"Privacy" is something one could aim for, if one has _control_. But IMHO without control, "privacy" is nothing more than marketing