So what building recipe are you using for KLV?
I use @wiak 's FirstRib build script that follow a PLUG file recipe which looks just like a shell script to build a rootfs and then using another script which extracts the Void Linux kernel and modules if used and builds a initrd.gz (initrd.img) for it. KLV was designed to also use Puppy Linux huge kernels or Debian derivative kernels as well as the actual Void Linux kernels. Updating kernels in KLV is right now a manual job.
The KLV scripts build distro's that use OverlayFS and not AUFS and what comes out of the scripts at this point still needs manual work to put together a finished boot-able ISO. It would be possible to do what you've suggested with some work on the PLUG recipe but the finished distro would be more like FIrstRib - KLV because of the differences. Our best strategy would be to continue to work with woof-CE. And finally get a grip on how to actually use it.
There is no getting around it, I'll have to learn how to woof to get all these good ideas now in F96 into a Jammy recipe to at least come close to a finished polished distro generated by woof-CE.
For now let's finish this one and bring to the goal line despite the shortcomings and once it's on the real Puppy Linux repos and listed on Distrowatch we can go all in on getting Jammypup as complete as possible.
bigpup could take a look at the missing F96 documentation needed for a release and write us some text. We all know much work there is left to do to create even the basic manuals and package + version list. Lot's of work to do on all the Puppy Linux documentation and tutorials.
We need to get bigpup and myself up to speed on Github submissions and pull requests so bigpup can get excited about the projects and contribute the important stuff