Alright, v0.3.1. As always,
grab it on GitHub, notes below.
To elaborate on the bug, it seems that for whatever reason any thread I create on the Switch's fourth core doesn't run at all. Since this is where I was running the audio code, of course it stopped working. The bug even affects the original release! This can only mean that it's a problem with some external factor; most likely Atmosphère or Horizon. Anyways, the audio now runs on the first core. It shouldn't affect performance because melonDS is run on the second core and the threaded 3D renderer is on the third. The only reason I avoided the main core before is because that's where the system is running and there are less resources there. It should be fine for just the audio though. Well, I guess input processing and framebuffer drawing are on there too, but it'll still be fine. Nothing intensive.
Anyways, lesson learned: test on an actual system before releasing.
@OkazakiTheOtaku I'll add your forwarder to the OP, thanks!