Considering the pivotal argument for the implicit children change is that all the other excess props are rejected so why would we treat children any differently.
How about the fact that no other prop, excess or not, is accessed, processed, handled in any particular way by react, yet children is?
How about the fact that furthermore, children prop has some very specific rules it must abide, depending on its type - the scope of key prop are ultimately siblings, yet it is enforced through children?
How about the fact that no other prop is explicitly frozen (Object.freeze) yet children is?
How about the fact that no other prop facilitates construction of the DOM tree nor attachment to it?

I get it. You like it simple, generic, elegant. Exceptions hurt, are ugly and nobody likes them. But the thing is, whether we like them or not doesn't change the actual engine this is supposed to annotate and it is this exact change that makes children implicit. It blatantly ignores and obfuscates behaviour that's an integral part of the API. Apart from that, the only purpose this served was that of an impediment to updating react to 18.

This whole endeavour is quite simply flabberghasting.