What you describe (“put that data into my code build”) only works with internal storage, and there’s just 128kb available (including everything else in your patch). There’s some planned solution with data loader in Daisy roadmap - probably in fairly distant future.
Also, my OWL port for Daisy Patch does use that 8Mb for storing data as well as multiple patches. OWL uses data encoded in Sysex for this (as well as bootloader and firmware updates and patch uploads).
Unfortunately libDaisy has a somewhat incomplete MIDI implementation, Sysex handling is missing there too. So even imitating this (i.e. separate patch that handles uploads and another one that reads data from QSPI) would not be very easy.