[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Thanks for the good opinion - but based on what I saw in the linked thread and linkd device configuration, it is indeed a different device: HD1925 and its codename seems to be hotdogg (with the 2nd 'g' at the end). So I am pretty sure, you cannot use my build on your 5G 7T Pro. I don't know, how the flash mechanism for 'payload' builds (the a/b stuff) works, I can't directly identify the assertion, whether the ROM could be flashed at all or not, but I would expect difficulties, if you try to flash my ROM and the flashing wouldn't immediately be refused... So I am afraid you would have to live with your build...

I consider the dev very knowledgeable and I don't have any issue with him (in the contrary, I have learned important things), but his specific way of communicating for sure is misunderstood / mistaken by many folks . . .

And his issue with Magisk in fact is that Magisk needs to "punch a big hole" into the SELinux rule set, because you need to allow to "transition" the SELinux context, which is a common attack vector (this however isn't a specific Magisk weakness, but a common weakness to all solutions allowing an ordinary "untrusted" user app to ask for root permissions).

Yes, indeed - similar device preferences :) - Well, I too am desperately waiting for a fully functional TWRP for our device, so my "tweak" version of Lineage recovery is the work-around for now, but not really my preference.

I will however, this is my "next project" for this build, to work on a kind of "ugly hack" (see below) - but maybe some knowledgeable person has a better idea. I'll try to describe my issue:

The official Lineage recovery, which can be downloaded from LinegeOS servers, won't flash my ROM (Probably, because of the signing key, but no idea - as said, I don't know, how the payload a/b flashing really works)

The Lineage recovery, which is built as a "side product" during the build process (and packed into the ROM), doesn't work either (Probably, because some of the hardening measures of my ROM cause problems during the sideload process)

So I've built the recovery along with an "ordinary" LineageOS with my signing keys, but besides the keys 100% identical to LineageOS sources and w/o any sec. patches of my ROM- et voilà, that one works (hence linked in OP)

However, every time, when an update is flashed, the recovery is replaced and thus scrapped, so before e.g. doing anything with recovery, my "special" recovery linked in the OP has to be flashed first from fastboot.

So my intended "ugly hack" would be to simply always pack my "special" recovery into each ROM zip as a prebuilt. I am sure, that'll work, but this really will become an ugly hack.

But maybe somebody of you have a better idea?

Such as:

Tell the build system not to pack the recovery image into the ROM and also tell the payload of the ROM not to attempt to replace the recovery partition? No idea, how and whether that would be possible at all?

Adapt the dependencies of the recovery code to build a working recovery along my ROM, so "somehow" build a working recovery, while still applying the sec. patches to my ROM...? Again, no idea how...

So any clue from a tech. expert is very welcome ;)