I assume you mean not whether it was loaded via http vs local — since that’s fairly straightforward (and doesn’t require a ping).
But if it’s not that, then it seems you want to know, in real time, whether the server is available and connected. So the question is: how often would you want this to update? And, with a service like TiddlyHost (especially given its backup history archive service), why would this be any better than having auto-save, with a clear notification of failure to save (presumably because of lack of connection to server)?
(I do think that a clearer notification of failure to save — or better persistence of the “Saving…” notification until/unless “Saved” is confirmed — is a good request!)
Is your worry more about the possibility of TiddlyHost (or some othe specific server) being down (or no longer having your login credentials active), or is it more about whether a laptop (say) is currently connected to the internet during a commute — which could obviously change at any moment?
Either way, having a frequent empty handshake with the server seems like a costly (computing/bandwidth) way to have only a 99.x% guarantee that your next save will work (given that internet connection can still be lost between the time of your last ping and the time you attempt to save to server).
Of course, I’d be happy to be persuaded otherwise. Maybe a once per minute check would not be too costly, and could yield a visually clear shift that helps remind me that I need to be mindful of the need to make local saves… (For similar reasons, I have a page-background-color difference between “reader” and “author” mode for public projects hosted on TiddlyWiki. Since I often check in another browser account to ensure things are displaying as they should for student visitors, it’s helpful for that load-instance to have a different background color. It doesn’t mean the server’s not “online” — but it does help inhibit me from jumping in to make a quick edit, since I’m not authenticated for this session.)