This is literally the question I started this thread with and you have gone in to a loop of saying “they can’t enforce this” without any response of substance.
If you are going to make guidelines, make them evaluable. These aren't. If you care about memory safety, either say use a memory safe language or point to an exact reference guide to use to allow XYZ language to satisfy it.
If you would pause for a second and actually read the rules in their entirety it is obvious that the lines you’re fixating on aren’t meant to be absolute security measures and therefore don’t need to be continuously evaluated.
Your conjecture about Apple withholding the permissions for arbitrary reasons is not borne out of evidence. When asked REPEATEDLY to show where they’re giving themselves an exception to their own rules, you continuously fail to provide any example and are just hand waiving conjectures.
Maybe they are doing what you’re saying but you’re making an incredibly poor argument regarding it.