In another post, I have uploaded and documented a minirt init modification handling cloop and squashfs transparently for the user, just using cheatcode "squashfs". It's for pure 64-bits, but the modification for 32-bits is trivial.
IMHO, present day squashfs seems to be about as stable, efficient and versatile as we need for this kind of use, and its widespread and growing use indicates others think the same.
So, with a "uni-minirt", KNOPPIX may still be distributed as cloop image, but subsequent remasterings will not have to unpack minirt.gz to make modifications in order to turn to squashfs. I think lots of remasterers will prefer squashfs, as it gives (at least) slightly simpler and faster workflow with at least as good results. OTOH. I can't see anything right now forcing us to use squashfs.
And, just for the record: This is not about the practicality or usability of cloop per se, but about the actual Knoppix use case.
Custom Server 15" Depth X11SSH-F E3-1270 V6 3.8Ghz 4 Core - 128GB NVME 32GB RAM
$399.00
1U BareMetal pfsense opnsense Router Firewall DNS Server 6x 10GB Ethernet Ports
$149.00
Australia Linux Server- 32 GB RAM + 500 HDD + 6 Core processor
$66.77
POGO Linux WEBWARE 1150 Rack-Mount Server Pentium 4 2.8GHz 512MB - No Drives
$179.99
1U Server 15" Depth X11SSH-F E3-1270 V6 3.8Ghz 4 Core 32GB RAM 240G SSD
$320.00
IBM Power8 S822L 20-Core 3.42GHz 256Gb 1.2Tb 40G Elastic Storage Server 5148-22L
$599.95
1U 10 SFF Bay Supermicro Server X10DRW-iT 2x Xeon E5-2690 V4 128GB DDR4 RAM
$399.00
Linux 23 in 1 Bootable Windows Alternative Collection Live Distro Mint Ubuntu OS
$18.95
SQL Server 2022 Standard Unlimited Cores
$510.93
SQL Server 2019 Standard 16 Core 10 User CAL DVD Pack
$370.42