In permissive compliance mode you ask forgiveness not permission, or better yet, you don't even let them know. When the auditors come by you make sure they see you meet all their checkboxes, even if you actually don't. Example: a video streaming company that always uses the same DRM key, decrypts video as it arrives, passes unencrypted video blocks around willy-nilly over a VPN and re-encrypts it just before it's sent to a customer. They have a successful product because they have a lot of flexibility and low constraints. They pass audits because auditors find what they're looking for (all outgoing streams encrypted).
Obstructive compliance is failing on the side of denying access. This is what people do when they think the point of compliance is to strictly meet the criteria all the time. If they're not sure about anything it gets denied. Example: a video streaming company that strictly never decrypts the source's DRM and passes encrypted video blocks around, and only stores keys wrapped in some security layers, will have quite a lot of difficulty delivering features like timeshift.
The most successful businesses do permissive compliance, but part of being permissive is looking like you're being obstructive, so that gets copied.
They are trying to coerce these companies into proactively removing anything that could even be inferred to be violating.
Which will hurt users more and save the companies a lot of work.
So yeah it seems to be more of a feature than a bug to me.