Okay I was doing a list of system variables for myself when I came up with some interesting facts and what I say may be a partial solution--partial as I don't know if the file had gotten some other problems/corruption that is not showing at the moment. I am going to offer some steps/explanation of what I did; if you want to try them out, you probably want to use a test file and perhaps back up all your customization/sysvar/settings in case these steps mess up your acad.
So I was probably editing the source of an array when AutoCAD crashed as the recovered file imply, as during the array source editing all other objects are "faded" and the ribbon has the arrayclose options. What this suggest is that interestingly the variable ARRAYEDITSTATE is actually "saved" with the drawing. You can check this by Edit Source for an array and use the setvar command/lisp which return the value On or 1, but return Off or 0 if you're out of the array editing; and interestingly it's possible to "save" the variable in the drawing by using setvar thru a Lisp Expression (setvar "arrayeditstate" 1) and then a save (you don't even have to have any array selected or in the file!), then compare the variable value for this test file and a new file. Note that you can't set the variable with the regular setvar COMMAND as the variable returns "Read-only", nor can you "save" the variable to the drawing while you are for real in Edit Source (by selecting an array and go edit its source) as AutoCAD prevent those actions and you do actually have a checked out array--it seems to only work with that setvar LISP. Now when I did that house I had no knowledge of LISP so it must have happened automatically and done by AutoCAD somehow, as when I recovered the file the array is probably no longer checked out, hence the arrayclose command won't function and is probably why an audit didn't fix anything, but the variable and the "visual style" didn't get "restored" accordingly. Also it's interesting that this variable can be set like this while some other Read-Only variable will actually return an error saying whatever value you want to set is not possible, and there are other such lisp-modifiable variable (ARRAYCREATION is another one I found that "save" to a drawing) while other similar variable like HATCHCREATION is not saved in a drawing but stick around even after closing the file and fix itself with a program restart or a lisp setvar.
So if you had tried the above and saved ARRAYEDITSTATE like my file seems to have done, just turn the state off with (setvar "arrayeditstate" 0) or create a new array and edit its source; the arrayclose command and its ribbon equivalent (save/discard changes) won't work as no array is actually checked out. And during the ARRAYEDITSTATE the visual style is modified but that may get stuck like mine, which seems to be a "old bug" related to Edit Xref In-place as suggested by this post: https://forums.autodesk.com/t5/autocad-forum/conceptual-visual-style-faded/td-p/7275097 so just reset the visual style in the visual style manager pane. If you try to do another array edit source it might not fade, and that might be fixed with just a restart of acad at least for me--maybe it's a graphic card issue...don't know. Still, I think it would be prudent to copy the objects to a new file if you can as you don't know if something got "corrupted" during all of the above; as I mentioned before I wasn't too far in my file so I just redrew the things instead of copying the objects--not quite sure if some of my objects was corrupted as well.
