no

take a look at the code, does it read a peers.dat file into a data structure from the config directory? If yes, you could run a modern version of Bitcoin to collect some peer IP addresses (you'll need to find other peers with older versions too) into it's peer.dat, then copy that into the config dir for the bitcoin 0.1 executable. If not, you'll have to make the changes to the 0.1.3 source to either read a pre-populated peers.dat file, or implement the DNS seeder code into 0.1 source, and compile it successfully. The code to read the peers.dat file is gonna be easier, I would expect. It'll still get stuck when you sync the first block >500 KB, on account of that problem with unpatched BDB library