For reasons I’m not entirely clear on, the gateway side implementation of translation/localization is considered an implementation detail. It’s unlikely to change between Ignition versions for pragmatic reasons (we don’t change our codebase much if something works) but you should be aware of the possibility - we might refactor things in our codebase which would make your calls stop working.
You’re in a bit of a grey area re: ‘supported’. You absolutely can’t call/email into support and expect help with scripting like this, and, in general, manually calling internal Java methods on the gateway can be ‘dangerous’ - you could cause any number of unintended side effects if you call certain methods.
For this use case, I think it’s fine, and it’s reasonable to want to fill this gap in first-party functionality - that’s why I shared the script in the first thread, and why I felt it reasonable to share in this thread.