It's a real pity, that Ahk2exe requires a fixed structure / a real installation of AutoHotkey (including Registry entries).
I've had planned to provide (within the company I work for) some compiled AHK-scripts via our deployment systems (using a VirtualMachine via Jenkins to do the compilation process and to build the releases/exes). As the VirtualMachines should not be permanently manipulated,our policy does not allow to install Autohotkey there (creating registry settings). I hoped the directory structure I mentioned above would allow me to bring the "complete" AHK-environment (including AutoHotkey itself, the Compiler and my script with all it's dependencies) to the VirtualMachine temporarily, compile the script and remove the whole environment without leaving any traces. Having the current situation (with the need of an installed AutohotHotkey) I currently don't know how to compile on a "naked" machine without a real installation of AutoHotkey, which would violate our policies.
Side remark - even if I would be allowed to install AutoHotkey: since my build may run on one of many build agents, I do not wish to maintain a suite of preinstalled software like AutoHotkey on multiple agents.