Does it even make sense for AdHell/SABS to struggle in order to correct those odd Chrome behaviors? I'm not a Chrome user except for testing, but doesn't simply disabling Async DNS in Chrome (and other Chrome-based browsers that also bypass the OS DNS) solve the problem without any bearing over other apps ... until Google finds another creative way to complicate matters?
BTW, note that some providers (especially satellite-based ISPs) silently intercept and reroute all DNS requests, but that's a whole other can of worms...