If the author had taken a bit of their own advice and went out of their comfort zone they might not have been having so many issues finding where to put the save file years ago! Overall though I get it and image distribution is easier for 99% of cases. I have found it more difficult in 2 cases though, both are cases of "the tooling knows ISO".
The first is on IP KVM's, even when they support non-ISO based virtual drives you'll often be wishing they did. The last I remember trying to futz with this was a Lantronix Spider and it wanted to pass through an entire drive letter but it wasn't working for whatever reason and I eventually just made an ISO with the files in it and mounted the file with 2 clicks.
The second is virtual machines with a similar story but this time it's usually possible to qemu-convert or extract and put into a virtual disk of the right format and you're good to mount the disk - or maybe you get lucky and the packaged format is just a click or config line away from natively mounting like assigning an ISO to a virtual CD drive is. A good example of the latter was just today I wanted to boot a live Linux environment to run gparted on an existing guest VM on an M1 Mac Parallel's guest. I had 0 knowledge (or desire) to investigate how to get an ARM64 image of my preferred distro to be in whatever format Parallel's expects just to use for 5 minutes then never use that virtual disk again so I found Fedora shipped ARM64 ISOs and was able to easily mount it with a few clicks in the GUI and do my work.
I don't think either of these are at the forefront of Puppy's use cases but worth mentioning in a universal call to retire ISO. It may be an old hodge-podge at this point but most everything understands how to work with it as boot media already vs whatever disk image format you choose instead.