Hi Shadowflyer11,
I am aware of the videos the PC team put out, however because the PC version is still in alpha and items can be removed if they don't work out for the team I would not bank on everything mentioned in videos. While the team will work to port as much as they possible nothing is confirmed to be coming to console unless it is announced by the console team, regardless of the work required if it is possible to port them. I recommend, if you wish to watch the PC videos, that you keep this in mind.
To the best of my knowlegdge, the analytics system that was added to the game was to track each time an error occurs (not what caused it), by doing this they can confirm after a patch that the fix for certain MD5 triggers has worked for players as the number or occurrences will go down.
They team are continuing to work on the remaining, more difficult to fix triggers.
As I mentioned before, blocks can not save you from the MD5 error because it occurs to the save file as a whole as it is trying to load. Even if they could, you would need to know what triggered it to write the code for it - which would lead to a fix anyway, making recoding a block an unnecessary bandaid. But blocks can not prevent MD5 errors. The errors occur because the save file struggles to load an area (In the past this could be due to loot trying to reset, there was a particular tree causing issues once, etc). Rather than leaving a void in the chunk it can no longer load it resets the area to the day one state, blocks and all, it is a blanket issue, not just a blocks one.
I understand my explanations may not be great because I can envision the hierarchy of the game from experience. If like I can try break it down into a simple analogy. Or if you have any questions about any particular part I will try explain better.
Clare