From a manufacturer's POV, this is easily solved in one of 2 ways, or both. Firstly, get the firmware right to start with or use a generic DSP that is proven and doesn't need to be updated, and keep the programmers the eff away from stuff that is working fine. Second approach is to do it the JBL M2 way with external amps with DSP in them.The flip side to this is reliability. Personally, I've never had a passive loudspeaker fail on me, but I've had multiple amps fail. In fact, my Yamaha Aventage RX880 just failed a couple days ago. Had this amp been inside of an active loudspeaker, I'd be SOL; I'd have to send it back to the manufacturer for repair, which is no fun. Don't mean to pick on JBL here, but go read the JBL 705p threads over on ASR, or the JBL 700 series threads here on AVS. These loudspeakers are far more prone to error than similarly priced passives. I see people in those threads that have gone through 3-4 705Ps in the span of 5 years. You never see that kind of unreliability with passive speakers. Another good example to go read is the D&D 8C thread over on ASR. Those speakers have failed multiple times for multiple people, not because the amps failed, but because D&D pushes out firmware updates with bugs that crash the electronics. Those people are left with a $10k piece of furniture until the devs can push out an update to fix the bug.
I've been building active speakers for more than 30 years, and sometimes I get the itch to put the amps inside, then lose it when I realise all the work involved. Whilst I've never had an amp fail, as I have several others around it would take me about 1/2 to load another one in and get it back to full function. With the M2 approach, a customer could simply hire one whilst in for repair, load in the settings and be running again.