[Magisk] Telperion:
Questions at the bottom, background info on the problem and logs below (all logs generated from Core Only mode on v12):

Problem statement: Beginning with Magisk 11.5, on many/most/(all?) current Huawei devices (problem still exists in recent v13 builds), the fingerprint sensor stops working when MagiskHide is enabled at boot time.

Workaround: Disable MagiskHide in Magisk Manager and reboot device, fingerprint sensor works. Open Magisk Manager, enable MagiskHide, and now both the fingerprint sensor

and

MagiskHide work (SafetyNet passes).

Snippet #1 -- Log with MagiskHide enabled, directly after device boot (non-working FPS)

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
post-fs-data.d: /magisk/.core/post-fs-data.d/buildprop_edit
* Loading core props
** Magisk late_start service mode running...
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
* Starting MagiskHide
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.verifiedbootstate'='green'
Existing property: 'ro.boot.verifiedbootstate'='ORANGE'
Recheck property: 'ro.boot.verifiedbootstate'='green'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.flash.locked'='1'
Existing property: 'ro.boot.flash.locked'='0'
Recheck property: 'ro.boot.flash.locked'='1'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.veritymode'='enforcing'
Existing property: 'ro.boot.veritymode'='eio'
Recheck property: 'ro.boot.veritymode'='enforcing'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=mnt:[4026532984] Zygote(1) ns=mnt:[4026532976]
MagiskHide: com.google.android.gms.unstable(PID=4748 ns=mnt:[4026533128])
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)

Snippet #2 -- Log with MagiskHide disabled, directly after device boot (working FPS)

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
post-fs-data.d: /magisk/.core/post-fs-data.d/buildprop_edit
* Loading core props
** Magisk late_start service mode running...
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d

Snippet #3 -- Log directly after MagiskHide is enabled from Magisk Manager (working FPS)

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
post-fs-data.d: /magisk/.core/post-fs-data.d/buildprop_edit
* Loading core props
** Magisk late_start service mode running...
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.verifiedbootstate'='green'
Existing property: 'ro.boot.verifiedbootstate'='ORANGE'
Recheck property: 'ro.boot.verifiedbootstate'='green'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.flash.locked'='1'
Existing property: 'ro.boot.flash.locked'='0'
Recheck property: 'ro.boot.flash.locked'='1'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.veritymode'='enforcing'
Existing property: 'ro.boot.veritymode'='eio'
Recheck property: 'ro.boot.veritymode'='enforcing'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=mnt:[4026532969] Zygote(1) ns=mnt:[4026532977]
MagiskHide: com.google.android.gms.unstable(PID=5193 ns=mnt:[4026533091])
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)

Snippet #4 -- Log directly after Magisk Manager has performed a SafetyNet test (passes green, working FPS)

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
post-fs-data.d: /magisk/.core/post-fs-data.d/buildprop_edit
* Loading core props
** Magisk late_start service mode running...
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.verifiedbootstate'='green'
Existing property: 'ro.boot.verifiedbootstate'='ORANGE'
Recheck property: 'ro.boot.verifiedbootstate'='green'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.flash.locked'='1'
Existing property: 'ro.boot.flash.locked'='0'
Recheck property: 'ro.boot.flash.locked'='1'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.veritymode'='enforcing'
Existing property: 'ro.boot.veritymode'='eio'
Recheck property: 'ro.boot.veritymode'='enforcing'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=mnt:[4026532969] Zygote(1) ns=mnt:[4026532977]
MagiskHide: com.google.android.gms.unstable(PID=5193 ns=mnt:[4026533091])
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)
MagiskHide: com.google.android.gms.unstable(PID=6273 ns=mnt:[4026533028])
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)

Snippet #1 and Snippet #3 are essentially identical, other than an informational message in the log on #1, reading "* Starting MagiskHide". There's nothing in the Magisk log as far as I can tell that shows why MagiskHide breaks Huawei's FPS on boot but doesn't break it when enabled after boot. Those with more Magisk experience than me, do you see anything in the logs that I'm missing that explains why 1 method works and 1 doesn't?

If Magisk's logs don't show the problem, next up I'm going to need to move onto grabbing kernel logcats most likely or something similar to compare what's going on in each boot scenario. If this is the route I need to go, which device or kernel logs do I need to grab? Even if it's beyond the scope of what this thread can help, if you can help me figure out what I need to save to start debugging it, then I can hopefully eventually make this an actionable issue on Github.