1. Settings for deciding which Foundation libraries to load may come handy. Version 2 of the plugin doesn't seem to load any unneeded libraries by default, so the benefit would mainly be to give users an easy way to enable additional ones they want to use.
2. I remember Google PageSpeed Insights stating that small scripts are more efficient to be served as part of other scripts, or even inline, although that disables browser-side caching. The sites that need this the most usually use a specific plugin to combine scripts, but if there was an easy way to include the half-a-kilobyte library/Foundation/js/foundation.custom.js inside another file, that would avoid the overhead of one server request.