Samsung Devices.. root access and securestorage working

I stumbled onto something that's worth some discussion..
if nothing else.. id love to just be told why I might be an idiot and why this is actually going to cause more issues.

SO as most of you that have a rooted samsung device know, that as soon as you root (even with knox at 0x0) the system image no longer passes dm-verity check and goes from official to custom.
this breaks stuff that uses securestorage such as SHealth, and Private Mode.. and even wifi password storage..
the fix is to simply edit the build prop and turn off secure storage (shealth and wifi come back private mode doesnt)
THIS ISN'T NEW INFO... heres the part thats new and that I would like discussed..

LONG STORY SHORT
If you edit your build prop and put back ro.securestorage.support to true
and then change
persist.sys.storage_preload to 0 .... this is where the discussion comes in
then......
private mode works no problems at all!! (persists across reboot)
shealth works no problems at all!!
wifi passwords still retain!! (not the first time from switching back to securestorage but afterwards--WHICH IS something you must note and a new bug in itself because all your wifi networks will incorrectly attempt to connect until you forget and readd them.)

soooooo what persist.sys.storage_preload actually doing?? because I definitely want both secure storage and root

discuss!