It system itself can be done. The real question is, do you need to?
If you want to make a desktop game that takes advantage of local files for storage, do it properly and make a desktop game with nw.js. If you're making a web game, use localstorage or other online based database.
Either way, is your game actually running into memory limitations? In a 2d engine like Construct, you're more likely to run into texture memory bottlenecks before system memory, and chunk based loading isn't going to help you very much with that.
Also note that if you have a proper procedural generation design, you don't save entire chunks of data to storage, you only save changes and differences. Those are very small and normally can be kept in memory all the time, only writing to storage when saving. And then as mentioned above you'll want to write it to the proper storage media for your platform.
If you've got a river to cross, try a boat first, no need to learn how to build a railroad bridge and a train first just because someone else did. Systems like chunk based dynamic loading are often designed to solve specific problems, problems that you may or may not have in the first place. Basically I'd say the better approach is to build your game first, and then apply solutions to solve the problems you're actually having. For example, if you had your procedural generation system in place already, you'll gain a much better understanding of what exactly you'll need to save and load, and how to best go about it, if you need to at all.