I think a better way to look at it, is that it does not introduce those issues in the first place.

It might seem like a nit pick, but incidental complexity like solving all the issues surrounding multirepos are usually accidentally introduced by not fully appreciating the tooling choices you have made. It's how simple products become overengineered nightmares.

Incidental complexity is any problem not directly related to solving your core business problems.

It solves the problem of code change visibility and synchronicity. Organizational architecture is not the same as software architecture regardless of how close they may look at times.