Here's an odd thought I've been toying with. LUA is insanely easy to host. What would be the benefits/possibilities of injecting a LUA host into WoW.exe?
But wait, you say, there's already a LUA hosted in WoW. Yes, but it's a crippled LUA possibly tied to Warden checks. An injected LUA couldn't bypass the Warden checks in cfuncs, but you'd know that anything you called in YOUR LUA would be as safe as your cave was. Also, dealing with the WoW LUA stack would no longer be a problem since you could (in theory) just snatch the stack for your own LUA.
Also, the benefits of having a scripting engine tied to your hack shouldn't be underestimated; this makes changing hacks trivial (no need to unload DLL's and reinject), it shortens the development cycle for behavioral changes (for bots and such).
It's probably not on anyone's to-do list, and it might even be impossible (if hosting two LUA instances isn't possible), but it's an interesting thought-experiment...