Tesla's Superchargers need to be like ChargePoint's in informing users how many are chargers are in use for a particular site and the number left remaining. Tesla are you listening?
The problem with that is the information you've described would only be helpful if you are both close to the station and able to easily reach the next one - and even then, the information on the next station would be dangerously obsolete by the time you got near it, and you might have a delay there that's longer than the one you would have had at the original station.
Having said that, I think there is an opportunity here, and I'm pretty sure you'll see Tesla creating firmware to take advantage of it eventually. As I've pointed out a couple of times, what you need isn't the current status of the Supercharger - it's the status it will have when you would get there. The problem is, no one can know the future, right?
Well, Tesla can. Or at least, Tesla can model it with fairly good accuracy if they assemble all of the data they have access to. Tesla knows the real time status of every charger, the charging habits of every car, and the navigation plans of all the cars on longer trips using built in navigation.
With that information, Tesla can not only predict that the three cars eastbound out of Silverthrone and the four westbound out of Limon are all going to meet at the Denver area just as the afternoon rush draws local or semi-local folks to the chargers, but they can try to mitigate it - use the navigation to route some cars to Denver and others to Lone Tree so that neither site overloads (or if the crush is bad enough, so that both sites have about the same overload.)
This is how I'd expect it to work. Tesla would build a (weekly? monthly?) historical model for the local/semi-local non-Navigation usage, and use it to predict stall availability for a given time on a given day. As each car gets a navigation through superchargers request handed to it by the driver, it would go to a Tesla server and put up estimated arrival times.
When the model suggests an overload, the server would hand back an alternate set of superchargers instead (where possible - right now there are a lot of chains where this isn't really doable, but it'll become more practical in more places as time goes on. Even single route chains might be mostly deconflicted by charging a little higher at some stations and a little less at others.) Just like the traffic routing part of the Navigation, it'll consider multiple options and give you back the trip that should be the shortest time for you - including both current/anticipated traffic volume and anticipated supercharger delays.
No user would ever be forced to follow the route plan and schedule or leave a station "on time", but most likely enough folks would that Tesla can avoid most of the delays and get a lot more usage out of the same group of stations.
(Implicit in making this work is getting reliable models of each car's energy usage in the actual weather conditions and realistic supercharger routing in Navigation, but I believe both of those are well within Tesla's grasp right now - the car can see in real time the actual consumption relative to both speed and acceleration in addition to real time weather and forecasts, so it should be easily able to compensate for you putting three people in the car or adding a bicycle on the roof from the actual energy consumption as well as head winds and freezing rain. The data's all there, easily in Tesla's reach. It just takes smart code to take advantage of it.

)
Walter