NOPE !!!
You thought I didn't test Zygist before posting the different variants of Magisk till Magisk v24 ??? lol
Magisks post v23 were mostly written for the Oppo, Xiaomi and then Nexus/Pixel devices, but Samsung Galaxy devices were not taking into account in the devs's priority if not at all !
I follow most of the discussions in the development of the Magisk forks and no one even owns a Samsung devices or even care about Samsung.
There was a bug in Magisk v23 that causes bootloop in most newer Android devices (a fstab story) and instead of simply patching Magisk, they decided to take Magisk all apart with a fork for Oppo, another one for Xiaomi and then one for the Nexus/Pixel all with a different philosophy... Instead of Magisk Hide which was removed, then created new concepts of "Deny List" and/or "White list" but which work differently from the previous Magisk Hide !!!
Zygist doesn't work, or at least not with the Samsung Galaxy !!!
- First, it disables riru framework and EdXposed/LSposed modules and thus all modules based on them won't work anymore such as XprivacyLua, Firefds Kit and some others... Only AfWall++ continues working...
- Then, once rooted with magisk with Zygist on, I couldn't get any protected Samsung apps working such as Secure Folder, Samsung Health is working only partly as I can run it once but I can't access to it anymore unless I reboot the phone. Samsung Health is working in the background as I can see its notification and the number of steps I walked during the day (...), but once again I can't access to the inner of the apps and I don't have access to the health parameters... Samsung Pay also won't work and others I don't use...
ATM I'm still fighting with Android studio to understand how I can build my own Magisk app for the Samsung Galaxy devices...