For most people, it wouldn't come in handy. For someone developing client connectivity software though it could really give you a jumpstart. Consider the alternative of looking thru manuals and various online databases, for urls and default creds each model.
Then figure out the right Wireshark filters to pull out only the relevant RTSP tags and write a nice db-loadable report of just the parts you want.
Tell me how long that takes.
As a dev in this field not knowing how to use wireshark would just make you a contracted code monkey in a 3rd world country that gets told to code a specific peice a code for a specific function in a specific language after all the hard work(planning and thinking) has been done. also what you have done is a low grade Wireshark on a specific port which you would have had to have known what and how rtsp is and how it works to know what you are looking for. I am afraid it would only take about 10 mins on google to find that looking to listen for a port and filter those results as that filter method is wireshark 101. But hey everyone has a "tool" they prefer so if you find what you did is easiesr than wireshark thats fine.
nothing ispyconnect ... can't give you.
i love ispyconnect, don't get me wrong. But it is an absolute mess of duplication and riddled with user tagging errors. But, the real thing missing in ispyconnect is the ordering of most likely to least likely, as I'm sure your familiar with. A well written discoverer plays the odds, and will go for the URL's most likely at first. Which if you are trying to save time discovering 50 unknown cameras is important.
I am going to assume you didnt understand or I didnt explain well enough what I meant by a SQLdump instead of taking what I said out of context. A SQLdump is a copy of the SQL database on a machine. Milestone, ispyconnect, ONSSI, Exacq,etc all use a SQL databse to store their data including what they pull for RTSP URL's. If you were to copy those and import those into another database you would have far more data and be able to easily, from a Dev's position, use that data for developing an app quicker and more reliable than anything a few printed urls in a file that you would have spend time importing into another database. not to mention that none of the URL's have stream/channel identfiers which would be in the database under a differnent database name within SQL after it did a discovery search.
most discovery tools that I have dealt with that are proprietary to their respective brands actually use SNMP. so for example Panasonic has a IP utility to search just for Panasonic cameras with a private MIB to find the model, IP, etc and so on. then after it finds its cameras it uses that infomation to go further such as rtsp streams locations, resoultions, SD card locations, etc, etc. all of the other major brands have something simliar and the major VMS companys would use that beofore trying to find rtsp stream locations as that would be faster and more reliable than "guessing" what rtsp streams are out there on the network broad casting.
As I said before its a neat trick (not being sarcastic) but there are far better ways for Dev to get and use data than the way you are using. most of us just borrow form the dev pages or other programs as its easier that way.