It seems to me that you have a non-issue here...
You have 8GB of files that you want to keep synced between your account on the server and your laptop. 8GB seems quite large to me, but let's say for grins that this is comprised of several large spreadsheets, could be any type of files, that you will be updating while offsite for the day, could be week or month I guess.
You connect the laptop to the network, turn on the sync client and in a few seconds you have the latest versions of the files. Presumably you were connected to AC power so there is no battery life hit. The sync client should now be turned off.
You are ready to go, you disconnect from the network and go on your merry way. You use your laptop as normal and update the required files as needed during your time offsite.
When you get back to the office, you connect the laptop to the network and turn the sync client on. In a few minutes the new files are on the server and you are back in sync. Turn the sync client back off there is no need for it until the next trip.
During this entire process the logs show when you transferred the files to your laptop so when matched with travel logs the IT department knows when the files left the premises, what they contained, where you were going with them, when they came back, etc... And, with the versioning turned on, the whole mess can be rolled back if you completely screwed up while you were gone.
Syncing of files has been going on for years, it is relatively easy to keep track of thousands of files of whatever size on numerous machines with the correct logging procedures and corporate policies.
None of this has any bearing on the poll interval of the sync client or the use of inotify or any need to trust anything. Client control of the sync process seems most economical. The server detecting changes on the server process can be helpful when creating a mirror on another server, ala rsync, but, that is not ownCloud's lot in life.