Read access I agree. But how does the system know the user (or bad guy) will only be "reading" and not modifying the file? That's the problem. And then what happens? Microsoft gets blamed for allowing the user to mess it up, or allowing the bad guy to intentionally corrupt or delete it.
That's the balancing act problem MS has had for years. Do they make it easier for the bad guys by giving users maximum flexibility to shoot themselves in the foot and potentially break Windows - and then get blamed for allowing it to happen? Or does MS lock the system down to keep users from hurting themselves and keep the bad guys out, then get blamed for taking away that flexibility? Its a no-win situation for Microsoft. There will always be some who will bash Microsoft regardless.
XP was very flexible and a tweakers joy. But so often users tweaked it to death and the bad guys exploited the heck out of it - and Microsoft got the blame. W10 is not very flexible and as such, is much harder for users to tweak and for bad guys to exploit - and Microsoft still gets the blame.
As a tech who was often tasked to fix those XP systems users tweaked to death and bad guys broke, I personally applaud Microsoft for making W10 much more robust and secure - even if it means I myself (who generally knows what I am doing), cannot tweak some things.
Some things just must be "for the greater good".