So, ive never read through this thread, only glancing at the title. But today I was digging around to see if there was news on the many many broken things (like images). And... I noticed that this says /boot was fried. Which.. yeah is a bad thing. But one of the least bad things that could go wrong as far as losing a partition goes. To be honest, boot is one of the easiest to fix. 99.999% of content is NOT on /boot. you have your kernel, and the linux image needed to... you guessed it, boot. But these get modified every time you update a kernel (often when they go missing or get corrupted and I get a ticket to fix it). These can usually be fixed with a "close enough" version to get the server back up. Hell, half the time I boot a "thumb drive" linux and mount / (the partition with all the content) and go from there.
So... long story short (yes, I know, I type a lot... its a disease... sue me), losing /boot should not have lost your content. Am I to assume that when you saw /boot was gone, either you decided (or your host incorrectly advised you) that you needed to restore a backup? If so, fucking ouch man. With KVM or console access, that could have been fixed in 5 minutes. Boot from KVM or a recovery distro (any reputable host should have this available, you prob have access to it in your hosting panel), reinstall the bootloader and kernel, then reboot. The exact process depends in the distro you are running sometimes, but its usually a 5-10 minute process with the booting into KVM being the longest part.
Anyways, all of this was to say that missing /boot should not have lost site content. No, the OS itself is not stored on there, just the bootloader and kernel. So unless you restored (which would be the actual cause of the data loss), that likely did not cause data loss (site content, etc).