All I mean to say is that I'm often tempted to try and figure-out the seed(s) used to generate the puzzle keys, as I think you've spent quite a lot of time doing... But every time I think about it, I have to remind myself that we just don't know enough / have enough data about where to start... Which version of which language was used, and which RNG (standard or cryptographic, Mersenne Twister or something else, etc) was used, or whether the rand was seeded once, before the loop with a static seed (like I tend to do, which I think is kind-of a common C# pattern) or again on every loop with a dynamically changing seed (the way the code you posted was), not to mention the seed's exact value itself, and who knows what other factors...
In 2015, a Puzzle BTC creator using Python + Electrum would likely have:
Generated keys via random.seed() (not PBKDF2/HMAC-SHA512).
Used WIF format (easily imported into Electrum using importprivkey) and ignored BIP-32/39.
This kept the puzzle simple, reproducible, and Electrum-friendly.
Consistent with real 2015 examples like 1FLAMEN6, which used raw SHA-256/RIPEMD160 hashes (not HD wallets) and WIF keys.
But who cares if I'm right or wrong?
