This looks like an injected library to me... even if it's manually mapped, it's still injected.
Thx, nice bot. Btw, There is only 1 warden module, but yes some scans have been omitted to keep the post relevant.
Look there is no e-peen here, that is difficult to express without a lot of verbose (losing track of what matters). It's just everyone needs to get their head out of the sand and stop pretending Warden cannot see them.
The last major banwave in Starcraft 2 was cause by a hack not cleaning up the thread entry-point into a manually mapped library. It was only a handful of bytes in size yet it got countless people banned, proving Blizzard will target any hack trail, no matter how large.
Your hack can pretend to be whatever you want it to be, but at the end of the day Blizzard only need to target a handful of rogue bytes in their process to issue a ban wave.
The combined warden scan count hits 137, It's very naive to just assume all those scans are for maphacks/zoom hacks and not the most popular bots online.
Solution? Study the DLL I posted up, or PM me privately for advice. Once you have established 100% that warden cannot see you, then you can focus on the server-side detection mechanisms. Guess work and debating isn't going to secure bots against Blizzard.