I mean theoretically it will still be faster since incremental-dom now see's less Node's for every root, but I thing the memory usage will probably way higher.
Angular doesn't use incremental-dom, but yes, incremental-dom could walk smaller subtrees. incremental-dom could also walk smaller subtrees by calling it on small containers too. That's probably already the common pattern for componentized users of incremental-dom. I'm not sure why the memory usage would be much higher.
I have an additional node. considering I change a upper shadow-root which has 50+ shadow-roots it's 50 more node's.
We have lists which have a component per cell and per row which is like 100x10 lines. That would mean 1000 x 2 node's more? Changing the whole table would probably be way slower without the inner shadow-root's.
Like ebidel mentions, the developer side is important too. You get to write simpler selectors and know that you aren't accidentally styling other parts of the document. I'd go so far as to say that Shadow DOM fixes most of the problems with CSS.