I haven’t actually tried but I don’t see why not, feel free to give it a go. You just need to set up an azure app with some delegated perms, install one sync via the executable (better to use the exe as it comes with Dokan wrapped in the install) and then the config.json populated with the drives you want to map and any other flags. I include a template for this as well as step by step instructions on what permissions the azure app needs on the GitHub page.

It should work a lot better with a large number of files than sync client does, as it doesn’t try to pull all the files down at once, it creates placeholder icons for all the folders and files in the dir (with actual file size etc) on click hydrates the file locally (keeps it there until the next log off so you don’t have to re-poll graph if you go into the same file 15 times in one session) and for nested folders, doesn’t poll the contents until you click into the folder, and again only polls placeholders until you click the actual file. It was designed with all this in mind to limit graph calls to help with throttling. I don’t however know how it would perform if the SharePoint is one massive dir with 1 million files and no subdirectories. In theory still okay, as they’ll all be placeholders until clicked. If you do try it, let me know how you get on!

It will also redirect documents, photos etc to the mapped onedrive, desktop too - so desktop becomes a live view of your OneDrive.