I have documented all my old hex edits so adding them to dll will be simple.

Unleashed was originally based on the standalone maped by BlackPhantom to be used, being able to run the editor with around 16MB of data only. It became useful to add LOD support at some point and that is when I decided to make all of Unleashed text be loaded through txt file in LOD.

Now I can perform simple check to see if Unleashed.dll is being loaded via ERA or H3Unleashed and disable some hooks, but I still need to be able to load Unleashed.lod from custom path. Simplest would be to get h3wmapedpatch's function and call that with path to Unleashed.lod which is why I wondered whether you could export that function... if not I can always get it from memory or even read data from the LOD myself; I just try to seek the option with least amount of work))

If you prefer to add Unleashed as a 'mod' and provide path to Unleashed.lod that way, that works too I suppose.
I can just disable LOD support when loaded by ERA and let it handle that part of the work.