The screenshot refers to a hardware fix, not a firmware fix. Possibly the root cause of the problem isn't or wasn't known.
I'd be worried that the tech disconnected the MCIs, but didn't record this activity. I can't imagine Tesla issuing in writing a service instruction which potentially puts firefighters in danger, nor can I easily imagine that the tech would commit his "fix" to writing either. This is not a inconsequential code violation--presumably there is a sticker that announces that a RSD system is in place. If Tesla is monitoring your production, they won't see an issue, and won't try to upgrade your hardware.
This apparently puts your installation in a difficult situation. If the root cause is hardware, it is likely that nothing will be done, because your system is producing reasonable power.
If it is a firmware issue, it may well have already been fixed, but you have no way of recognizing that a fix has taken place.
My unsolicited advice is to carefully demonstrate that your MCIs aren't hooked up. Use the M Tool app and take screen shots to show that you have production and no MCIs. Write an email with the screen shots contained in the body and as an attachment. Point out that this is not code compliant and unsafe. Request them to rectify the situation immediately. Wait 3 days and if you receive no useful response, call and stay on the line until you reach a live person. Insist on speaking to technical support because Tesla has a real safety issue and legal liability here. I believe that once anyone at Tesla realizes that they have installed an unsafe system, and that the issue has been documented, you will get a quick resolution. Of course, at some point in the interactions, you should push for replacement of all the MCIs, or at least a commitment to replace them if performance is degraded after reconnection. Again, I think the key is to use email to document, and phone to get attention.