Hi Flamingskull,
I am away from home for a few days but the package should work really well in any install.
However I see I've utilised the "spawns" column in the global layer and some people are uncomfortable making mods and anyway if you don't have MS Excel or similar its not so easy modifying the global layer csv file.
The thing is, I'm not totally sure its necessary. You could take the modified sub pen and port facilities, and add the spawns, and try them in ETO. The ship xdps can go in ETO but apart from the sub xdp are probably optional - I included the ship xdps in stock to ensure there were working small ships of the "patrol" type.
As for the frontend.xml in the missions folder - that is a little bit of fun for stock cfs3 - it enables spawns to appear in the ui while you are watching the pilot stooge about on the opening scene. Sometimes if your air.spawns file allows enemy bombers to spawn over friendly territory, you can watch your airfield get bombed before you've even selected a mission!
So for ETO, I would start by adding the spawn files, facility files and ship xdp files if the same ships are in ETO, and see if the coastal shipping spawns without the need to mod the global layer.
Let us know if it works! It definitely would work if you modified the global layer files too but I'm suggesting a simplified process to save you the trouble.