I could help with the work if you could not do it by yourself.
The big question is if OP knows part or most of it. If he knows no part of seed/private key chances of recovery are very very small.
If he is trying to brute force it there is just to many options. This is what keeps wallets secure is it being pretty much impossible to brute force.
But there are more effective options than bruteforce like dictionaries + masks/tokenfiles. Wallets like Armory are lot more resistant as they implement several hundred of hashing rounds, but other ones are plausible to attacks, knowing facts like there is already working implementations in GPU of several of the wallets encryption algorithms.
How does hashing multiple times help anything? If we're using a dictionary attack, it doesn't matter if it was hashed 1x or 10000x -- after the hashing was done, it would return a true or false based on the input password. No amount of hashing is going to make that change. It would only help with rainbow attacks (where you use an existing hash you know the password to and run that against a database of hashes to see if anything matches).
500 rounds of hashing instead of one increments the hashing time several orders of magnitude.