I'd call that design error #1.
Until you need a second or third language, and you are screwed.
And you are still processing string lookups for many tags that aren't being watched.
For such a poorly designed project, I would construct a shared document tag with two layers of keys--outer enum "type" and inner state value to lookup. I would ensure the result strings were unique translation keys. Then any tag value that needs lookup and translation can just have custom tag property indicating the enum "type" for lookup.
UDTs stay lean. Lookup values are centralized. No excess computation is performed.