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.
Samsung 850 EVO 500 GB SSD 2.5 inch (MZ-75E500 AM) Solid State Drive
$25.00
LOT OF 10 Mixed 256GB M.2 NVMe SSD
$120.00
SAMSUNG Solid State Drive 990 PRO Series - 1TB, Sealed
$99.99
Samsung SE-506CB/RSBD Slim Portable USB Blu-ray Reader/Writer
$35.00
Samsung 870 EVO EQV 2.5" SATA III Internal SSD - Choose from 1TB 2TB Capacities
$54.00
Samsung 870 EVO 2TB 2.5" SATA III Internal SSD (MZ-77E2T0B/AM)
$139.99
Samsung USB 3.2 Gen 1 Type-C 256GB Flash Drive MUF-256DA/AM
$19.95
Case For Samsung Galaxy Tab A9/ A9+ 5G/ A9 Plus Kids Shockproof Cover with Stand
$16.99
Samsung 1.6TB SSD SAS 2.5" 12G PM1635 MZILS1T6HCHP-000C3 NetApp 520 Block
$69.95
OEM Samsung Galaxy Tab S9 Ultra 14.6" Book Cover Keyboard, Black, EF-DX915UBEGUJ
$199.99