I didn't look into PoS too heavily. Considering most of the code appears to be a direct yacoin fork with the bare minimal alterations to function, and their PoS still works, I'd expect it to be alright. The real problem, is the orphan problem. Without a DNSseed, longer block/retarget time, etc, this will remain a large problem. Its something that could easily be fixed via a hard-fork, but the only real way to get that to happen is for cryptsy to agree to fork their wallet as well. (Make the money fork, and the miners follow). If it were hardforked, could also include coincontrol, and look at PoS pretty easily at that time as well, but as I say, both those features are luxuries compared to the orphan issue.

When trying to rebuild the database -- it will be stuck on the splash screen for a long time, and be "unresponsive" (I.E. if you click the icon, or splash icon, windows will tell you the program is not responding, linux will do nothing -- this is why I recommend running with logtimestamps, so you can see it is still adding the blocks from disk. Its painful either way, but atleast rebuilding isn't too bad.

Technically you should be able to interrupt the process and resume it (as it will likely take 100% usage from a core, and significant disk usage), but as there is no way to "cleanly" exit, you do run the risk of corrupting the new database. FWIW, when I reindexed on my WinXP laptop for testing, it kept going to hibernate, and would wake up and resume indexing w/o issue.

Both prebuilt binaries I've posted (Windows/Ubuntu) contain the respective most recent version of openSSL, which fixes heartbleed. If you built it yourself, it will use whatever you have installed.