I'd like to preface that my response is speculative... but I doubt FIRST has any specific plans for the current sensors. They are provided for Teams use how ever they seem fit, it at all. Most teams will do just fine without current sensing (like a majority do now).
Remember, as of right now, the only way to have access to the current readings is to wireup the CAN bus between the Rio and the PDP.
In order for FIRST to pull off what you are proposing, they would have to force every team to wire that bus, and have default code on the RoboRio that reads current off those channels.
I am not an expert on FMS/Driverstation communications, but as far as I know, the Driverstation only talks to a small part of code on the cRIO to control Robot State, and UDP a couple of status parameters back.
While it is possible for FIRST to pull off something like what you suggest, I think it is very unlikely that they ever will. Usually a stalled Motor is not the cause of a Robot loosing comms unless it is pulling the batter voltage down below the brownout point of the CRIO or D-link. The #1 priority of FIRST FTA'a is to make sure your Robot maintains FMS connectivity, not diagnose your build faults: that what other gracious teams help with

.
Frankly, I would rather FIRST limit the amount of reach they have within User code than expand it.
Hope this helps,
Kevin