I think this is similar to you for sure. The inability to save is maybe unique but the other behavior is very similar.
DJST says this in the latter part of the post:
So there’s still this lingering data ghost bug on there. I’ve had a similar problem in the past where upon booting it up, some patterns were erased. I’ve learned to always reload the project when starting just in case, but this is the first time it not only erased patterns, but replaced then with the contents of a totally different project.
I’m guessing that when a project is loaded, it doesn’t actually erase the data on each pattern, instead it probably just has a flag that indicates whether a pattern is “in use” or “blank”. And then I assume that during power cycles some data corruption occurs that makes those states change - both ways, meaning both “erasing” active patterns and resurrecting unused patterns from previous load states. Kind of like how apps like unerase can recover permanently deleted files from a disk or hard drive. 
Is it doing the weird behavior every time now?