That’s pretty much the subtext of bans anyway. To guarantee undetectable use the contributor must treat gen code like a junior’s draft and refactor prior to PR. If it’s undetectable, the end result is the same from the maintainer’s perspective.
And it’s not a new approach. This has long been true for contributions containing “found” code; we define what’s allowed knowing we can’t actually enforce the rule against the most artfully obfuscated violations because, aside from achieving ostensibly the same result, having that tappable sign protects the project from a lot of BS down the line.