Yes, it definitely makes sense but it's a bit different than my situation. Mine is something more like...
Computer A - Running Insync, with target folder pointing to a network share.
Computer B, C, D, etc. - Not running Insync, but have access to the same network share.
From computer A, if a file is created or edited in the Google Drive folder, then that change is detected and the folder is synced with the remote Google Drive folder. Ok, just what we want in that case.
Now, if computer B was to create or edit a file in that same folder (via the network share), computer A will NOT detect that change and the folder will NOT be synced.
In your case, when a file is changed in your Google Drive folder from within Windows 10 let's say, that change syncs when you reboot back into Ubuntu. This isn't much different than my situation if I were to restart computer A as needed. At that point any changes made from computer B, C or D would be picked up and synced. However, I'm not sure how fast your Insync starts up, but mine literally takes DAYS to load, sign-in and do a full sync (even when there are no files that need to be synced). It's somewhat understandable considering its checking TB's of data against a network share, but at the same time, it makes restarting to solve issues like this not viable.
It would be great if there were one of two things available.
(1) That Insync properly watches that folder and detects changes made by anyone and kicks off a sync.
(2) Built into the shell or menu system, where I could select a folder and tell Insync to force re-check just that folder (or something similar to that). This is not the greatest solution, but in my case would be a million times better than restarting computer A and have all syncing halted for days while it starts back up.
Hope that clarifies my situation a little better. Thanks for the reply!