Sure, if it's not verified then parental controls could skip the feature entirely and still do whatever blocking they want as normal. This is a terrible argument that it doesn't take anything away from parental controls. It's literally pushing the decision away from parental controls onto the platforms and legislators, with an opinion that it should be based on specific buckets and content that have been legislated, and now parents and developers have to think about both the local blocking and remote blocking matrix.

Maybe I actually like the defaults for some age range blocking and want to make an exception. So, what, parental controls that would like to support this now must implement lying to each app or website individually?