Maintain children of an element while calling importDOM

[ChanManChan]

<RootEditor>
             .......
              <LexicalNestedComposer>
                            ..........

When calling importDOM, both outer and inner composers fights for the same node. It is very tedious to brand all the markup generated by each level with a unique id so that they can stay within their contexts. Is there an easy way to keep contexts separate when nesting Composers?

Example:-
MentionNode Inside the caption of an ImageNode

Here the caption is a nested editor

In the exportDOM function of the ImageNode I'm structuring it like so (crude example)

<div>
     <img src="....
      <span class="image-caption-container.....
             <span class="mention" data-lexical-mention........

The mention node gets pulled out of the 'image-caption-container' (which is supposed to be for the inner composer state) and then gets inserted into the root level editor DOM. Not the expected behavior, this causes confusion since the DOM elements jumps around when re initializing.

Can we solve this issue in an easy way? Am I missing something obvious? Is this supposed to work out of the box but did I mess something up in my custom configuration?