The main issue here is that there’s a mismatch between userspace perception of state versus that of the kernel driver, and no standardized way to push that information (unless you make your desktop environment add that info by polling the filesystem driver)

Users definitely don’t want blocking dialogs if the userspace visible state is already updated enough to keep working. And ideally your software would check what kind of drive you’re using and report to you when it’s actually fully done as you close the program, but like I said this isn’t standardize