In some cases it might work. But me personally I like to use the string/index object to have as many different loops available when the patch is live. Ilike to switch between them when the patch is live. For this Axoloti would not know which files I am loading after the patch is made live, so in this scenario converting on the go wont work. Also all loops I make has to fit perfectly in table, so for this I need to do a lot of "manual labour" on the files anyway, like sample rate convert, stretch files to fit table etc. And for doing these things I have to use an audio editor. The only difference in the workflow is exporting the file as raw instead of wav. Not an issue here.
But sure, if you have an idea how to code your way around the header click, I think everyone would be interested and welcome it
(Also would be awesome to remove the "BLLLLLIP" when changing content of a table when a patch is live. To me that is a bigger deal than the raw files. So if you have an idea how to avoid that, it would be most welcome)