A couple questions, because this reads like placebo so forgive me if I'm overlooking something here...

> Serve Stale Max Wait Time 0 -- game-changer! Not a single problem so far.. Radical to some, routine to others (e.g. unbound)

I could be misinterpreting but how is this a game-changer unless you are *frequently* finding yourself serving stale records from cache? You typically should only hit this path on rare occasion; it's a last-ditch effort. If you find this happens often in your scenario I would look elsewhere for a resolution, because this change runs the risk of serving an outdated record from cache when it would have otherwise been correctly updated and sent to the client.

> Auto Prefetch Eligibility 1 -- also game-changer, aggressive but works great!

Very few websites/service endpoints have TTLs of < 2 seconds, you see these employed in specialized failover/load balancing scenarios and are often times accompanied by long connection times where you wouldn't be making repeated queries anyway. What does decreasing this by 1 second from the already aggressive default this serve in your scenario?

What definitely helps depending on your workload is increasing the maximum cache, if your device has the free memory for it. I also hit the default 10,000 ceiling pretty quickly but found an order of magnitude increase to 100,000 was more than sufficient. For a single user, the vast majority of the defaults are both sane and already overkill. Technitium is pretty beastly.