[Magisk] pndwal:
It's core functions still work fine... No essential issues AFAIK... It's only a user friendly resetprop tool UI after all.

Only it's named (common use) purpose... More below.

You can already add props for global spoofing in PIF .sh script files if you want... It's not hard and may be more versatile too... However using MHPC may be easier.

MHPC named purpose (configure props for MagiskHide, read "device integrity spoofing", purposes) is certainty superceded for devices running Android 8+... Zygisk based spoofing targeted to GMS DroidGuard actually fixes issues related to setting props globally, especially for fingerprint (MHPC Select fingerprint, which also alters security patch level) and model (MHPC 'Force BASIC attestation') prop setting from MHPC's pre-defined fingerprint-set list... Issues related to device/OEM specific functions (high end camera functions etc) and utilities (OEM backup, app stores like Galaxy Store, etc).

However you can simply avoid using these preset prop sets/superceded functions/menu items and still use it wherever you wish to set props globally...

Despite its name, MHPC is still the essential resetprop UI for spoofing props for any purposes globally that it always was, so it's far from obsolete for purposes other than magiskhide'/integrity verdict purposes in Android 8+ devices, and there are many such uses, edge case or otherwise...

Some Detailed Information on MHPC use, especially with devices running Android 7 and earlier:

From the perspective that until USNF (from 2.4.0 and earlier for @Displax 'mod' fork) began to spoof passing fingerprint props (for mismatch needed for PI DEVICE_INTEGRITY) this had become MHPC's key/only remaining needed function for'magiskhide'/integrity verdict purposes (ie. to achieve remaining prop config which was until then "out of scope" for USNF but needed for ROMs lacking passing fingerprint/security patch level combinations, ie custom, China region, developer etc) and was not needed since,

it could be said that MHPC had become obsolete for devices with Android 8+

since there's no longer any apparent need for it's global spoofing for 'magiskhide'/integrity verdict purposes... (Nb.while only devices launched with Android 8+ need the key PIF device fallback to BASIC-only attestation and server end HARDWARE_BACKED evaluationType verdict enforcement prop based bypassing, PIF can still be used on all devices running Android 8+ to provide needed setting of 'sensitive' props to non-suspicious values, passing fingerprint/security patch level combinations for custom, China region, developer ROMs etc, and root hiding for GSM DroidGuard and main processes)

Since PIF

is not needed for devices launched with Android 7 and earlier and

apparently cannot be used for devices running Android 7 and earlier

(nb. FWIW USNF supported Android 7+),

MHPC may still be used/useful for passing DEVICE_INTEGRITY (ie for 'magiskhide' purposes) on such devices

... These need 1) 'sensitive' ("MagiskHide") props set to non-suspicious values which MHPC does by default if loaded, 2) in the case of custom, China region, developer ROMs etc lacking passing fingerprint/security patch level combinations, such prop combinations provided by MHPC Fingerprint selection, and 3) root hidden from GSM DroidGuard and main processes by adding these, ie. Google Play Services com.google.android.gms.unstable and com.google.android.gms processes, to denylist, to meet DEVICES_INTEGRITY.

👀 PW