Unfortunately this appears to be wrong. I think in order to make this glitch-free you need to perform reconciliation locally. Because LV can teleport components you never know if a component will be remounted far away in the render cycle, so while you can fix this in most cases you can never provide a guarantee.
Perhaps this is what you were getting at? If so I just didn’t understand. This is actually a very interesting insight, as I thought the teleportation behavior was a neat trick but it would seem it’s actually a bit problematic. I’ll have to keep that in mind.
Unfortunately that means the glitchy behavior is the best we can do. But on the bright side it’s still better than nothing and I think we can hack together a working implementation in userspace…