So can someone correct me if I'm wrong but do the safegates only work in FSDT Airports?
Yes, at this moment.
If so I feel that this is an issue that has to be addressed as I paid to have to use of safegates
You paid for whole GSX, but you can't expect that all its features would work exactly the same on any airport or be always available in the same way.
You might say you also paid to get custom Pushback routes with custom labels (instead of generic Left/Right) and custom gate selection menus, and these also work only at FSDT airports or, at least, an airport we customized, because these are all features not accessible with the scenery customization editor, but requires programming, so they don't work at every airport.
There are reasons for this: is not that we don't want you to add the GSX safegates to any airport, it's just that the most common models are mounted on walls, which means they must be precisely adapted to each scenery and each gate AND, the stop position on ground must also be calibrated AND it must be possible to specify custom offsets for different airplane types.
It's not like the marshaller, whose position can be guessed based on the parking and airplane cockpit eyepoint, but it's not a problem if he's placed a bit ahead or back. Wall-mounted docking system must be exactly positioned to the terminal wall, and its height might need to be adjusted either.
The only docking systems that might possibly placed automatically, like a marshaller, are those based on ground, but still there will be the issue of having to define multiple stop positions for different airplane types.
GSX already has ALL these features internally, which we use at our airports, but we program them as a script, we don't have an easy to use graphical editor. This should be done as a GSX feature, if we expect end users will use it.
So, it's something we might add in the future, if only because it might be useful for us as well, same as defining custom Pushback routes, which is another thing we can do but users can't, but we need to write an editor, which is more complex than the current vehicle starting positions editor, and will be more complex to use anyway, because instead of just moving a vehicle in a roughly correct position, you will have to first choose the docking system type, position it very precisely to the terminal wall, set the reference stop position on ground, and set all the different offsets for the recognized airplane types. Multiply this for all the gates that have docking systems at an airport, and I fear not many users will create such files themselves so, you'll end up in a similar situation as of today: having to wait for us to create a customization for an airport.