A few days later i've had to call it, but since there's some good info here's mine:
System: 2500k @ 4.1, 1060 3gb, using latest nvidia drivers (also tested 271 and 266)
Was able to arrive at a min maxed config where upon first load, gpu usage was 30-50% when walking around a station interior, spikes up to 80+ were easily absorbed and it produced a constant 30fps at 1080, using decent image quality. Optimised even further by putting bloom and sharpening back via reshade than cobra, reshade was a 1 fps impact where odysee would explode, anyway.
Sadly odysee is literally unplayable for me. The problem is when you actually load into any scene with structure geometry. On second load, to anything, the engine immediately spikes to 100% and stays there. There is nothing possible to cure the load problem, and there's no amount of nerfing i could do to absorb it, or prevent the trigger. Tried low on everything and everything in between. Even found the volumetric fog on low bug etc. Im confident to conclude this is a frontier provided bug, because every single scene that becomes unplayable, even ground bases, becomes a smooth 40% load use if you exit the game completely and start again. All is great until you trigger the spike, fly anywhere, or turn the camera at the right corner geometry with the right effect on. GPU spike and unplayable.
Horizons of course is 60fps majesty on the same hardware. Shadow of the tomb raider with all settings maxed except for textures and maybe shadows down a notch benches a rock solid 30fps with a much lower frametime on the same hardware. The amount of detail that game is pushing out is an order of magnitude greater than an elite station.
The lure of carrier interiors will prevent it being deleted for the next 2 months though. And the fact they even sold this to existing players, even hinting at a 1060 being a minimum from my experience could be considered a technical fault.
EDIT: Yes out of the countless things i tried, getting vram usage to be under 3gb almost helped. But even with a regular presence at 2.8gb used didnt prevent the trigger.