Low privileged users able to use unconfined seccomp profile via restricted-v2 SCC

Issue

• While creating a pod/deployment with seccompProfile: Unconfined, why the pod's security context is matched against the restricted-v2 SCC given that restricted-v2 prohibits unconfined seccomp profiles?
• It's evident that the only Seccomp profile allowed is runtime/default

$ oc describe scc restricted-v2 | grep Seccomp
  Allowed Seccomp Profiles:         runtime/default