Before I became a full-time livestreamer, I was a network engineer and infrastructure support technician. I worked in a NOC that provided service to major US banks, and credit cards. Trust that I am well-versed.
I completely understand and agree that context and use case are critical to make such decisions. And there is user training/expertise in dealing with consequences of those choices.
As for being well-versed, I've been an IT Pro since '96 (PC expert since mid 80's) and for last ~10 years as Enterprise Architect (Infrastructure and Security) for a large (over 60K employees) global company. Prior to that I was server admin, handling thousands of servers. I've designed, installed, and managed FDA 510K regulated servers handling medical device in hospitals. And I do network work as well (I ran my own CAT5e in my house). I've managed corporate firewalls, VPN, etc. Yes, I know what I'm talking about.
In certain use cases, I don't disagree with running OBS as admin. But regularly... not a chance.. and recall, for original poster, for recording Google Meet class.... on PC with single storage device, etc.... lots of single points of failure... so lets get real. The reason for OP to run OBS as admin is older, low-end hardware and contention issues, not because it is a good idea
You mention one a certain use case (though I'd argue, if that critical, simply a more powerful PC is warranted, and some other redundancy) ... though again, depends on specifics and level of OS expertise. For 'mission critical', I'd be using NDI feeds to multiple targets, protected power, redundant LAN and WAN circuits on physically divergent path if at all possible, etc... yea, I've worked on medical device mfg plant network design, and others where downtime not acceptable). And for OBS streaming important single take events, there is the associated expertise in understanding and configuring the OS optimized for purpose, including making sure that unexpected tasks/processes don't kick off unexpectedly during a streaming/recording session.
For general user, and without a warning of potential implications (like security context of browser windows, 3rd party plug-ins, etc all without any, or much, code security review), generally recommending running OBS as admin strikes me as irresponsible/inappropriate (or a punt). My use case is livestreaming House of Worship, so also single take. Running OBS as admin on a dedicated, properly built for purpose streaming PC where there is plenty of resource headroom as-is (not even close to reaching any resource contention issues) and OS is properly configured, would be counter-productive/pointless.
So you can disagree strongly all you want, but you appear to be projecting your use case onto others and not providing a warning. So on this we'll disagree. In many other respects, I value your input regarding OBS to this community, and will usually defer to you and your OBS expertise