Hi @MaxMarschall ,
You inspired me to look into this again. In full honesty, it’s possible that I may need to revert the change I just made if I find that it creates more issues than it solves. It’s hard to know for sure because this issue is all in the somewhat nebulous realm of how Rhinocommon interprets the intersection tolerance, which we have had long discussion with the McNeel team about before. But I have implemented something that gives you what you expect for your case and it does not seem to disrupt the existing behavior so I’m hopeful that I should not need to revert it:
You can get the updated component now by running the LB Versioner.