I don't agree with you. To give you an example:
When you buy a software, you normally get a serial-number (which you can already save it in Enpass). But some software are providing a license-file instead of a serial number. This files are very small and I don't want to store dem separate in a encrypted folder. As I have written previously, for bigger data we can use encrypted folder, but license-files or key-files have in opinion the same priority as passwords.
Another point is the sync with the cloud. I don't know, how the development-team have implemented the sync function, but nowadays it's possible to sync only the changes between two files. Next today we have highspeed Internet and so the sync takes some seconds.
The last point (I don't want to attack you) if this feature is implemented, nobody forces you to use it. So if you don't attach documents to Enpass, the DB of Enpass will stay at the same size as it is now. It's fine that you only store passwords in Enpass, but in my case some files(cert,...) are used to authenticate me on some services. These files are used like passwords and for this reason I also want to store it in the same location as all my other passwords.