As far as I understand the fusion drive - it essentially is a JBOD and not Raid0.
It's neither of those - but it has the terrible reliability characteristics of RAID-0.
Other systems call "Fusion" by the term "volume concatenation". You have a logical volume (which appears to be a single disk drive to the unprivileged user) composed of multiple partitions on one or more physical drives. (Windows has been doing this since the last century, and all server class operating systems have similar features.)
"Fusion" takes a concatenated volume concept a step further, and lets the OS specify on which segment of the concatenated volume that certain files should be located. The OS knows which segments are faster, and can do some optimizations.
It's bloody stupid, however, to blindly put all OS files on the SSD.
It's good marketing, since you can have a keynote bakeoff and show that it "boots 57% faster".
However, I'd bet that few people reboot weekly, a fair number reboot monthly, and the majority every few months.
Most of the OS files are either not used (libraries for features or hardware that you don't use or have), or are touched once during boot and never again (initialization code, drivers that are moved into memory,...).
Why waste the SSD space with locking down those seldom-used files - instead of doing some more intelligent frequency of use placements?