I would be really happy if DJI only alerted me about "real problems" instead of making my drone a brick.
Like with the app which refused me to take off because it wanted to update. In the field, over 8 hours away from home. I lost a whole day that time. How was that a real problem? Everything worked, I just had an app version which could potentially be modified and give me more control over the drone. And I didn't modified it - just the fact that it was possible, that some hacker, somewhere, developed a modified version of that app - that was enough for Dji to make my drone unusable.
Or with firmware P3X_FW_V01.11.0020, which introduced strict checking of some ESC parameters - which resulted in the exact error described by OP - "ESC Status Error". Not due to issues, but due to firmware update. It was not an indicator of something being wrong, drones just had large spread of these parameters during production.
I asked OGs from Github about this - they said it was a bug fix - previous code was so sloppy that the checking function was inactive, and Dji didn't noticed.
They speculate that expected range of parameters coded there was never tested, because the buggy code didn't worked. So they coded a very strict checking - because during their tests, that never triggered ESC error. And then, strangely, they found that bug just at end of Ph3 support. A happy coincidence - as many people got "ESC Status Error" just at a right time to buy new Ph4.
All 3rd party flight helpers are based on Dji Mobile SDK. Developed by Dji. Supplied by Dji. Supported by Dji.
If Dji service even tries to bring that up, I'd treat it as a try to scam the user.
(I got a bit angry. but the issues I described really got under my skin)