Integrating the generation of the installer image into the current OpenWrt git tree would require quite a lot of structural changes. Currently we don't have a way to generate a specific per-device initramfs, and including yet another initramfs image as well as other build artifacts in an initramfs image (the installer) is completely out of scope.
What I was planning to do is simply to generate an installer based on 22.03.0 once it gets released.
I agree that forcing boot into recovery image based on pstore/ramoops may be confusing -- on the other hand it helps a lot to find and document hidden bugs which we do want to find and fix, so keeping it enabled has already brought as to a state where now (with nftables/firewall4 and no longer using the iptables flow-offloading hack) there just haven't been any reports of kernel crashes for months. In my opinion OpenWrt doesn't try to make a consumer-grade product but actually targets developers and enthusiasts, so I'm not feeling too bad about burdening users a bit if that results in overall better software quality (ie. meaningful bug reports of things which would otherwise go unnoticed).
This is kinda similar to the debate about the "reboot every 24h" cron-job you will find in some community mesh networks -- I understand the convenience and the need for it, but ultimately workarounds like this have the effect that things will just not get fixed and in the long-term you will then need to reboot (or live with kernel oops related reboots) more and more often.
Hence I'm tempted to just leave it on and maybe document it better (incl. how users can disable that feature) in the wiki.