Simplified way of maintaining blueprints (no zipping)

I just looked into blueprints. It seems they are simply a ZIP of the the site folder, with minimal config data in a json file under root. Wouldn’t it be better to keep that JSON there at all times and simply provide a checkbox in site settings about whether a particular site should be made available in the blueprints dropdown when creating a new site?

This way new sites could always be created based on the most current version of sites specified as blueprints rather than on old zip archives.

Especially cool if Local were to support automatic plugin updates some time in the future.