Perhaps you could expand … the recovery is now (and only recently started [1]) delivered as Recovery and boot img which is a “package” of required components as a .zip file. When extracted is found:
recovery-IMG-e-1.17-s-20231109350748-stable-avicii$ ls
dtbo-e-1.17-s-20231109350748-stable-avicii.img
dtbo-e-1.17-s-20231109350748-stable-avicii.img.sha256sum
recovery-e-1.17-s-20231109350748-stable-avicii.img
recovery-e-1.17-s-20231109350748-stable-avicii.img.sha256sum
vbmeta-e-1.17-s-20231109350748-stable-avicii.img
vbmeta-e-1.17-s-20231109350748-stable-avicii.img.sha256sum
As shown above each component has a checksum. Always best to check the sha256sum before use, or especially if there is suspected “some issue”. Or are you actually finding a checksum mismatch?
[1] Week 47 2023: Development and Testing Updates
Of course downgrade of Android 13 (T) Lineage 20 to Android 12 (S) is quite likely to be problematic.
The error SPL error however may simply be the result of the Lineage build having an Android Security Patch Level in advance of /e/OS 1.17; from release notes, https://gitlab.e.foundation/e/os/releases/-/releases,
This /e/OS v1.17 includes the Android security patches available until October.