That's a good idea that I should have thought of as soon as DNS over HTTPS servers became popular.

My remaining issue with DNS is how to avoid tracking from whichever DNS server you choose. In this case, the author is using an AdGuard client and presumably AdGuard's DNS servers. I do, too, currently, but I do not want to have to trust any server individually.

I envision an at-home DNS server which uses any number of upstream resolvers which could use any one of traditional DNS, DNS over TLS, DNS over HTTPS, or DNSSEC, as you choose. Then send requests for name resolution of random domains throughout the day. Keep some responses for longer than the given time to live. Allow some statistical analysis locally to check how well masked your network traffic is to tracking.

The random polling could also run on a computer on the network, I suppose. Have a script which browses sites randomly. "Randomly" would have to mean choosing intervals which obfuscate other traffic on the network, probably start with a Poisson distribution.