If you're concerned about privacy and are using windows, that's like buying a car with an internal combustion engine and trying desperately to figure out how you could convert it to be pulled by huskies.
Just use the right thing in the first place instead of fighting a losing war, or, just ignore that war raging on without you.
THIS.
It is a very straightforward approach to approach to 'personal' computing; either be your own OS and hardware Administrator by virtue of 'h4ving sk!llz' or you need to make the acquaintance of and/or hire one.
Either way, if your in-house geek is 'for real' about system security and privacy the conversation should at least include an option for QubesOS. (If your geek hasn't deployed it / hasn't heard of it, it might be because serious security geeks treat it like 'the first rule about fight club' - it might meansyou need a better geek.)
I've been the resident geek for most of my close associates for decades. Back in 2013 one of my brothers actually asked me not really in jest; "Where do i get my own foil hat, I always thought you were a bit over-sensitive to the whole network information security, but now I am too."
By now, even my centenarian grandfather uses a similar setup, including disposableVM's, domain specific vm instances, and windows in a network isolated use case for specific tasks. Yep, hes one of my first supported transitions after doing his own migration from Window$ to Ubuntu10.04 back when he was only in his 90's and some virus had messed up his Dell, "for the last time."
When helping someone move from being the product to owning their own systems a common question is "Why can't it still just be the way it was?" One line I use with pretty good results, is "It is not logically or realistically possible to be both better and the same."
Bytheway, Grandpa's 104, still walks the little dog for a couple miles every morning around dawn, and gets about better than most 70 year olds.
Actually, a skilled operator would have restored the logs to a state including all activity not-related to the incursion; left no traces within the compromised systems and the only (perhaps) discoverable traces would have been differences in total volume of network packet traffic as defined via the falsified logs and external network hardware/actual packet volume.
So, maybe this is a somewhat adept intrusion, but certainly not best skilled and only nation state type action. Plan B for that kind of hack; instead of false log trail; simply dd if=/dev/urand of=/target-system-root
"Consistency requires you to be as ignorant today as you were a year ago." -- Bernard Berenson