Question: When opening boot.img in Magisk can a recovery*.img be used when the boot.img is not in the e/OS/ version file?
To date I’ve always used the boot.img in the upgrade zip file. However with v3.0* there is no boot.img.
Somewhere on the forums a single individual suggested a recovery.img could be used in place of boot.ini.
Having never heard of this, I want to verify before giving this a go.
Thanks for any insight into this issue.
Since /e/ OS is a fork of LineageOS, I have always used the boot.img from Lineage because there is no boot.img from /e/ OS in the files for Poco F3.
Of course! Brilliant and thank you for your response. 
Am having difficulty finding the boot.img for Android 12 which is what version /e/OS’ v3.0* is.
Any working links?
Choose your phone from LineageOS Downloads and download the latest boot.img version
some clarification -
can a recovery*.img be used when the boot.img is not in the e/OS/ version file?
no, boot.img is the kernel you’ll be using during runtime, recovery.img is a recovery system with its own embedded kernel.
the /e/ boot.img is within the payload.bin of an /e/ OTA upgrade file (or anything that is adb sideloadable). You can get it with any payload dumper. It’s just that /e/ doesn’t publish them separately for ease of use (probably should?).
And as you noticed, it’s not necessary
If you use the boot.img from Lineage, you’ll be patching and using that kernel, not the /e/OS built kernel. But with most devices, esp. outside store devices, the kernels sources nor built options in /e/ will not differ to those upstream in Lineage.