Which isn't to say I think your use case is unreasonable or that I disagree with your assessment. But regardless of right or wrong straying from the golden path with SaaS is dangerous. With any software really, but SaaS is by far the most precarious. If it's not designed with your use case in mind it's not uncommon to run into bugs or deprecations.
My not-so-practical advice:
My first suggestion would be to evaluate if you really need that command and control or if it's something you're used to having. Once you let go of that dealing with Drive as an administrator becomes dramatically easier. The worst thing you have to deal with is recovering deleted data (available for 25 days) and complaints about the Windows/macOS clients which most people end up ditching as they realize the golden path there is the web interface. Obviously this depends a lot on management style and culture. Sometimes letting go is so hard that it hurts more than it helps even if you commit to it.
My second suggestion would be to evaluate if you're using the right tool for the job. fileshare@mydomain seems obvious but records@mydomain makes me think you're using a file sharing system for something that would be better served by purpose built software. Like a CRM or a document management system. Even an SMB share is a terrifying place to store structured data built around human processes that require them to follow rules and not delete things (even at small scales).
More practical:
Sync client: If bandwidth is constrained roll out the client to users in comfortably small increments.
Drive API: I may be misunderstanding your use case, but I think this is just as simple as logging in as the records user and authorizing the application instead of granting it global scope to the GSuite account. Here you're going against the grain in a couple different ways: That kind of access is meant for things like an interview scheduling system that needs read access to all calendars. The expectation is that apps that need access to a single account would simply get that access by asking the user for it.
Backups: Besides using the sync client and taking snapshot based backups from the local copy (which is a half-assed fragile hack) the only thing that makes sense is trusting Google. That's only fair to ask of you if we're not talking about data that would sink your business if lost. But if all of the data is that critical are you using the right tool for the job? Even a local SMB server setup would need to be carefully designed to account for the myriad ways you can lose data. If it's only a subset do you need to back it all up? Maybe what you really need to backup is a manageable subset.
Good luck. I hope you get this sorted out–it sounds like a huge headache.