@robains Without passing judgement, TileProxy was quite a hack compared to even some of the popular techniques today.
It utilized the old Pre-FSX method of loading uncompressed photoscenery from disk. It does this by intercepting file system calls from the FE system to load, and dynamically injecting downloaded and processed data into the contents of the file load request. It utilizes a closed source, kernel mode driver to do this that could be glitchy (by both the community and the author's own reports.) You can read about this here:
https://www.edtruthan.com/tileproxy/manual.htm#16
Because of this, it didn't support some of the highest resolution imagery of the new (for FSX) QMID64 system, and could only load the aerial texture tiles, not dem meshes nor full 3d objects like the city tiles. It does not replace the core FSX terrain engine or replace the existing tessellation / geometry stages, just modifies the texture that can be displayed.
We have a lot of experiencing operating in this low level space, but I would be firmly against delivering something like this and requiring an end user to escalate UEFI privileges to install an unsigned kernel mode driver that could affect system stability as a workaround for a needed Core API.