A Shadow DOM could ensure isolation between the two teams, but CSS namespacing is also a concern within a team, so CSS modules will just kill two birds with one stone here.
So they handle the upstream collisions nicely (i.e. the embedded content not affecting the parent site).
But the other side of it is the downstream (i.e. the parent site doing `div { color: black }` which propogates to the embedded content) and it won't handle that nicely.
You can do something like cleanslate does (https://github.com/premasagar/cleanslate) to aggressively unset so the parent sites CSS gets "disarmed". But it is not the smoothest and things like REM unit values still propagate to the embedded content.
I had to deal with this in a project using https://materializecss.com, and it was such an uphill battle to override these styles. Because apparently nobody considered that an application might have more than one kind of table https://materializecss.com/table.html.