[Magisk] zgfg:
Just a few more words from my side. I also like to have TWRP, and also mainly to be able to fix the bootloop problems with modules if they happen (it rarely happens to me but I like to know that I could fix it on my daily driver without factory reset). Also, I always install or update Magisk by patching and flashing boot.img and then I do flashing from TWRP (or even by disk-dumping from Terminal), not by Fastboot (I often do it on go or while watching TW or something)

Regarding to FBE (File Base Encryption) - it's mandatory by Google since like A10 and they make it harder to 'break" with every new version of Android and that's the main reason for delaying support in TWRP and other custom recoveries for the new Android versions. Even if you disable pin for unlocking the screen on Android, then Android still uses a default credentials to encrypt Data and Internal memory. There are custom ROMs that have disabled encryption

Do you maybe have device without Recovery partition, ie with Recovery integrated to Boot partition. Otherwise I don't see why would you have a problem to have Magisk (in Boot) and TWRP (in Recovery) in parallel

Btw, I do have such a device and I live with both Magisk and TWRP. It's important that you first install TWRP and the Magisk afterwards. That way, when I patch Magisk initially or later for updating Magisk, it doesn't affect the TWRP (I also used Orange Fox). But if you first patch Magisk to Boot and then you go to install TWRP or update it, it will for sure (it least, it always did for me), remove Magisk from the Ramdisk. But then I immediately make a backup of Boot, reboot to the System, patch that backup image of Boot from Magisk app (for patching a file root is not needed and although TWRP's Boot backup is named boot.emmc.win it is just the image file as boot IMG), reboot to TWRP and flash it - and then I again have both Magisk and TWRP in the same Boot partition

You cannot install TWRP from Magisk. It's not Magisk's business. But you can install some root apps that allow flashing from them. Or you can manually flash (or backup some partitions) by dd from Terminal. There is also a Magisk module where you can flash zips for TWRP (but not for installing/updating the ROM itself because you will be doing it from the live Android session)

----

Btw, yesterday I have encountered an interesting problem with my TWRP. It's an unofficial v3.0.7 version for my Xiaomi, supporting MIUI 14/A13 (official TWRP still does not support A13 and exactly bcs of the FBE)

That TWRP supports the FBE excellent for my device. In fact, I use Xiaomi.eu, it's a custom ROM (kind of debloated from official MIUI) and as that, it cannot be installed/OTA updated by the stock Xiaomi recovery. Therefore Xiaomi.eu uses custom recoveries (TWRP, SHRP, OFox - whatever becomes available for the particular device, even if not stable or fully working) and they even include it into the Xiaomi.eu ROM installations, to make them possible to implement OTA update for their ROM (updater downloads the OTA package, user confirms update and updater reboots to custom recovery and automatically trigger OTA flashing and when finished it automatically reboots to System - it works seemlessly for then user just like OTA update of the stock ROM with stock Recovery). Of course, that custom recovery must be able to deal with FBE, to read the downloaded Xiaomi.eu ROM (OTA) zip package

So far I didn't have any problem with that TWRP (in the last month since I updated Xiaomi.eu from MIUI 13/A12 to MUI 14/A13 and switched from OFox that I used with A12), I enter my pin, it decrypts for user 0, I can flash (that's what I used it for). Once I disabled a module (bootloop case) and I made some screenshots from TWRP and it all worked fine (reading and saving files to Data and Internal memory, reading read-only System, etc)

But yesterday I decided to do Backup from TWRP (not for System - for that I can dirty reflash the ROM), not for Boot (I already keep original and patched boot.img), not for Data (there are better ways to backup apps and their settings and data by eg Swift Backup root app) but for Persist, Cust, DTBO and so partitions

I made a backup and rebooted to System. TWRP folder was created but MiXPlorer (working with root grant) declared it empty. I tried Xiaomi (MIUI) File Explorer - the same. I tried from Terminal (with su), for ls -la it was empty. Well, no use, I wanted to delete but rm and rmdir responded that I (su) have no permissions to remove that TWRP directory. MiXPlorer was also not able to delete or rename that 'empty' TWRP folder it started to bother me because root checkers (Ruru, TB Checkers, Applist, Momo) find the TWRP folder and declare that phone is 'rooted' (pretty stupid 'method' but that's what really some 'banking' apps do among the other ways they use to inspect if the system is not modded)

Hence I rebooted back to TWRP and for that TWRP itself, the TWRP folder contained all those subfolders and 31 files, few GB in total. Then I used USB and MTP and transferred that TWRP backup files with no problem to PC (all from TWRP) and I finally deleted that 'empty' TWRP folder from TWRP and rebooted back to System (Android) and there was no more the 'empty" TWRP folder...