I had JamesDSP and V4A installed as well when I updated to Canary Magisk 24304 and got into a bootloop. I disabled all mods and then enabled one by one to see which one was causing it. V4A was fine (however I'm using a A12 version of 2.7.2.1) I'm fairly certain that I enabled AML, rebooted, and then got into a bootloop, without enabling JamesDSP first. However, It's possible that I enabled JamesDSP with AML at the same time, but I really don't think I did.
There are some other reports, however, that JamesDSP was causing their phone to bootloop when updating to Canary 24304. A user also reported that V4A was causing them bootloops on Canary 24304 (v. 2.7.2.1). They were on Android 11.
Sorry, but I didn't grab any logs as I was not certain you would be interested since it was a Canary version of Magisk (and frankly just forgot as well). I have since downgraded to Canary 24301 where JamesDSP, V4A and AML have been working fine together.
There were also some other changes to Canary 24304 aside from the sepolicy changes.
This commit to Canary 24304 was causing problems for another non-audio mod. Not sure if it could be related to the problems with the audio mods or not but may be worth taking a look at. It appears the Magisk people found a
fix for that mod and commit that I assume will be merged into the next Canary version.