I’m looking at a list of permissions here:

https://github.com/M66B/XPrivacy/blob/master/README.md

Most of these permissions either require individual consent after you run the app (and can be revoked in settings) or aren’t allowed under any circumstances.

The exceptions I see are:

Clipboard

Internet access (you can block cellular internet access on iOS and 3rd party keyboards can be blocked from allowing any network access)

Prevent links from opening in a view - depending on which type of web view that an app uses, the native content blocking framework that third party ad blockers use for Safari also work in the WebView. For instance, the ad blocker I have installed works with Feedly - my RSS reader.

The only sensor I think that can be blocked is the GPS.

XPrivacy is not about blocking, it's about faking.

PrivacyGuard in LineageOS is about blocking.

How is “faking” it better than just not allowing it all? iOS Developers have had to handle being denied permissions gracefully since 2008.

some apps don't work if the permissions are blocked. With xprivacy you can tell them

My phone number is 000 000 000 and my email is [email protected]

and they work fine then

And iOS doesn’t need that bandaid. App developers have been developing with the expectation that their apps could be denied permissions they request since day one.

Except for stuff that iOS doesn't ask and even implement a permission for. Like UIDevice.identifierForVendor.