What good is a performance designation (A2) if no device in the real world supports it?
I imagine Android would benefit the most (and phones also don't suffer from sudden power outages, which is the biggest risk with enabling this), so someone may try looking if mmc core in androind kernel has patches to support this.
Perhaps you have never dropped your phone, but in my experience, on a dropped phone the battery cover and the battery often go flying.
Phone batteries die, and the battery remaining percentages are only an estimate so writing code to react to that condition can be fickle.
this is often the case for new hardware specs/protocols..
see also: any SATA/SCSI rev N+1, TCQ/NCQ, UASP, PCI n+1, etc.
With A2, so far I have not seen any way any consumer (or anyone, really) could achieve 2000/4000 IOPS.
That would be like selling a SATA 2400 drive for 2x the cost of an SATA 600 drive... but not selling any kind of controller that could use more than SATA 600 bandwidth.
Spec/code is open. I'm just sort of surprised noone tried it yet.