Don't replicate a file server in SharePoint. You should instead look at breaking these out into multiple site collections. Banking, for example, should likely be it's own site collection, etc. Simply the layout by flattening it rather than trying to replicate the hierarchical nature of a file share. Also attempt to avoid permissions inheritance breaks like you would in a file share; use side-wide permissions instead.
SharePoint is security-trimmed, meaning if you don't have access to the object, you do not see it.
Storage limits are outlined at https://learn.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits#limits-by-plan; 1TB base storage +10GB/license. You can purchase more storage, as well. OneDrive has 1TB of storage but is designed for personal documents.
For OneDrive sync, don't sync that much. Teach users how to access documents from the web rather than attempting to synchronize everything. Don't attempt to use sync for >100K files.
SharePoint can replace a file server, but you need to structure it differently.
Can't answer on Dropbox, that is your call to make. SharePoint can ultimately replace your file server.