dnsproxy-config VS pihole-doth

Yes.

You can find the project here, the documentation describes installation alongside or in front of Pi-hole, depending on the use case. If you want secure incoming traffic, a certified FQDN is required. This is left as an exercise for the user (to raise the bar somewhat).

No need for the full AGH stack. You can easily run dnsproxy alongside or in front of Pi-hole.

I have somewhat documented the process of putting up a Do(H|T|Q)/DNScrypt proxy as a standalone service here.

I still need to fix up a couple of permission issues in my documentation, but I have the rough outline of deploying dnsproxy as a standalone simple service here. The last few edits I made to it were getting it to use the yaml syntaxed config file, and trying to make sure a default configuration should Just Work without having to edit it, but you'd still want to.

There's a basic overview here, but I haven't touched it for a while and the documentation may be slightly broken surrounding exec permissions on some files.

It's very possible. You could easily set this up yourself. I do so so myself using dnsproxy, and you could too.

I have an example dnsproxy service here that I use for high availability (one-to-many) distribution and providing encrypted transport.

You might know me as that Unbound guy, or maybe even that dnsproxy guy. Today I would like to make myself known as that Munin guy, and introduce munin-pihole-plugins for Munin Monitoring.

Kinda.

For assistance with this software, please visit the developer's site at https://github.com/camelstrike/pihole-doth/issues