makes sense as a policy stance even if enforcement is basically impossible. the signal it sends matters more than the enforcement mechanism.
similar to how some projects have DCO or CLA requirements — it's not foolproof but it sets a cultural standard for contributions. projects that care about their codebase provenance can at least point to a policy.
the quality argument is the more practical one imo. if LLM code in contributions correlates with subtle bugs or misunderstood requirements, it's reasonable to not want it regardless of copyright concerns.