There’s always a chance (with a damaged backup) things could go wrong. Worst result I guess is loss of the versions that seem good at the moment. Although this has been quite a deep dive so far, more diving would be possible if you want to either have the Python script look at your dlist and dindex files, or simply save your current database (rename is probably good) and see how Repair does on giving a clean one. If it gets to past about 70% on the progress bar (especially after 90%), there’s data missing, so it will be slow as it eventually downloads all dblocks to try to find data not in a dindex (as is normal).
Error: The socket has been shut down was another temporary communication error, but a DB recreate painfully built a database. What made it painful was the need to get dblock files. A special build helped.