Not with a TCP proxy. To establish a HTTPS tunnel, the client needs to know the identity of the remote end for certificate validation. Randomizing remote ends w

Not with a TCP proxy. To establish a HTTPS tunnel, the client needs to know the identity of the remote end for certificate validation. Randomizing remote ends with a naive proxy would lead to TLS errors. So you'd likely configure your browser to do DoH destined for that proxy, and have the proxy generate DoH requests to the remote ends. The downside is you'd have to somewhat manually set up certificate trust between your client and your proxy - either by trusting the proxy's certificate, or installing a root CA that issues the proxy's certificate in your browser's trust store.