Thank you for reaching out and reporting this problem, I was able to reproduce this behavior with the Direct-Link and udatasmith file with the Keep Hierarchy Method. Could you please report a bug by following this link so we can best investigate and follow-up on this issue.
The current workflow is to export only the elements that have animators/translators separately as a udatasmith file. The rest of the model can be imported using the Direct-Link. You will need to create 2 views in your Archicad view map one with the direct-link elements and one with the elements with Translators. This will avoid having duplicated elements and allow for better control with the updates.
Then import the udatasmith file using Keep Hierarchy for the Collapse method and only update those as needed. When updating them the Translator will not be deleted and you will have to reapply it to the elements. Unfortunately, this can be time consuming if there are a lot.
Thanks Vincent, yes it gets complex splitting up the export methods. It appears that the animators stay connected to native TM elements (ie characters) but break with imported items from archicad. Would be great to see this fixed on the next update