So there's two versions of FuseHFS; we were banging our head against patching 0.14 to work ever since it broke (sometime around High Sierra). Apple finally kindly fixed this for us by removing HFS support from the default filesystem bundle (instead of leaving an unusable stub in there like they had done before).
So 0.15 just has some tweaks to place the filesystem bundle in the correct place for modern macOS, and is otherwise indistinguishable from 0.14 that worked on OS X 10.6 - 10.11.
And as it's indistinguishable... it's essentially just hfsutils bundled up as a fsbundle. So it shares the same limitations as hfsutils.
I will throw in one more warning: FuseHFS can stomp on Apple's implementation of HFS+ as well, and THAT can cause some issues with GPT formatted disks. I've only ever had an issue once, and I fixed that by temporarily disabling MacFUSE and then re-enabling it, but there are definitely some minor differences.
That said, being able to load my HFS disk and CD images on Sonoma (on Apple Silicon) is a definite plus
Before I was having to boot into Linux to do it, which just felt wrong. So now I can prep my OS 9 images on Sonoma, then write them out to disk
[edit] And now I remembered what the edge case is for me -- When using HFSFuse, if you create a sparsebundle and format it HFS+, and then "convert" that image to a new sparsebundle (which traditionally frees up unused space), the sparsebundle will balloon to its max size, because diskutil doesn't think it can see inside the file system to free up space, and so pads with nulls instead of stripping them. Something to be aware of if you're using HFS(+) sparsebundles and HFSFuse.