Then, I expose my PiHole as a DoT + DoH server (DoT for Linux and Android, DoH for Firefox) so that I can always use my ad block lists and secured DNS traffic.
Maybe something exists for that already?
It's also an availability thing. There's that one archive website on a vendetta against cloudflare for not forwarding enough data in DNS requests (eDNS or something?) that I can access by using alternative servers as well. In the rare case of a cloudflare outage, this also ensures uptime.
DNS cannot be made fully anonymous, though that double encrypted DoH thing seems promising. Picking a few trusted providers isn't a problem for me personally.
I have a PiHole, and have the cloudflare DoH client installed on it.
Requests from my network go to the PiHole, and the PiHole is set to query localhost:5053, which then hits a DoH provider.
Why do you have separate setups for mobile vs. desktop web browser, why not have the OS do native DNS to your PiHole?
Similarly, I use DoT on my phone but if I want to connect to any hotspot, I have to disable DoT because the hotspot login detection fails with DoT configured. I think it's a Xiaomi thing. Regardless, I need to disable it to use. In one particular case (scanning groceries in the supermarket for the automated payout) I can't fall back to LTE like usual. Just in case I forget to turn DoT back on, I've also configured Firefox on my phone to use DoH because the mechanism is there and I might as well.
There's small edge cases where I just like to fall back to browser DoH. DoT and I'm network DNS still works fine, of course.
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.