I have been using dynamic text constants in the new framework for 6 months without this issue, including in 2015 2.2. Just in case it helps you to move past this issue, have you tried putting your dynamic constants in a module instead of a window?
Interesting. So either not many people are localising their desktop apps using dynamic constants (seems unlikely) or not many have switched their desktop apps to the new framework data types (seems more likely).