Quote - you might try loading the bits alone in a scene then resaving them with a different name to the library.  that should 'break' any superconforming in the cr2.  then use that copy, which shouldn't cause crosstalk anymore.  (assuming it's superconforming causing the problem).

Just do the experiment I mentioned - load M4, load v4 with lalibits, spread M4s legs

I had the problem months ago when testing P10 and I thought it was a P10 problem and reported it. It turned out to be a problem with how autoconforming was setup. In P10 it now includes a check on whether the figure is actually a conformed item. And that fixes it in that version. Breaking auto conforming/crosstalk by adding a figure number should fix it as well.

Or you could load V4 first