There's little data here on the PC, or the OS, let alone when you did this versus the recent updates to Elite (which cause binds issues for many). Lots of red herrings here, and you're probably just coincidentally being unlucky.
I will say, since you moved your RAM slots (and again, no hardware data to go on here) that you checked your motherboard manual to ensure it's happy you're running the RAM in the correct slots for that configuration? 1/3 and 2/4 are often exactly right, but some boards like 2/4 over 1/3 (or vice versa) to ensure the channel setup is correct based on the RAM speed/CPU-type (like certain AMD chips being more sensitive to RAM and locality to the associated chiplet).
That's still entirely irrelevant to whether your %appdata% directory would have its permissions changed or not, and how Elite would behave.
Games, not "like Elite", just games, are so far removed from the hardware via things like the OS, DirectX and the device-driver layers mean that, unless you made a major hardware change - and RAM is not one of the listed changes - Windows couldn't care less. The BIOS itself doesn't do self checks unless the amount and speed of the RAM changes. The location is merely a checked to ensure power hits the right pin. If you installed it incorrectly you'd likely not even get the system to POST, let alone let you in to Windows and see the OS affected in any meaningful way.
I played over the weekend with some friends. One booted the game up and had no binds. He had changed nothing.
He had backed his binds up.
He checked the directory - the binds were there.
He checked the contents; they matched his backup.
He replaced his binds.
The game worked.
I'm afraid this stuff just happens and we've both been in IT for 25 years; I've given up trying to work out how Windows does things these days, and having had decades in support, PCs work one day, then not the next. As a side note, my wife's headset microphone refused to work on Monday night on her work PC. I checked it on mine; worked fine. I worked through her PC settings and could verify it didn't work. Rebooting did nothing; I disabled the driver, rebooted, changed the settings and defaults - all the usual junk (that I could, given no admin rights); and the next morning it worked. The reason? I'll probably never know...
As many have said; back up your binds and if you have issues then replace them. Cleaning your fans did not cause this