Move JS to footer

On any site I build that has a bunch of module and theme js/css files I see that aggregation results in 4-6 css files and 4-6 JS files.
I understand this results from authors having the option to select from several CSS/JS GROUPS and make use of preprocess, cache, and every_page options in the add_js and add_css functions.

In all sites I've studied this resulted in needless addition of aggregation files. for many small sites it makes sense to just aggregate all frontend scripts / stylesheets to one file, so I put this code in my theme:

function arctica_js_alter(&$js){
	if ((variable_get('preprocess_js', '')) && (theme_get_setting('arctica_js_one'))) {
	  uasort($js, 'drupal_sort_css_js');
	  $i = 0;

	  foreach($js as $name => $script) {
	    $js[$name]['weight'] = $i++;
	    $js[$name]['group'] = JS_DEFAULT;
	    $js[$name]['every_page'] = TRUE;
	    $js[$name]['preprocess'] = TRUE;
	    $js[$name]['cache'] = TRUE;
	    $js[$name]['scope'] = 'header';
	    $js[$name]['version'] = '';
	  }
	}
}

function arctica_css_alter(&$css){
	if ((variable_get('preprocess_css', '')) && (theme_get_setting('arctica_css_one'))) {
	  uasort($css, 'drupal_sort_css_js');
	  $i = 0;

	  foreach($css as $name => $script) {
	    $css[$name]['weight'] = $i++;
	    $css[$name]['group'] = CSS_DEFAULT;
	    $css[$name]['every_page'] = TRUE;
	    $css[$name]['preprocess'] = TRUE;
	  }
	}
}

The result is that everything gets aggregated to one (or sometimes 2) Javascript and CSS file.
The $js[$name]['scope'] = 'header'; line is probably not the best idea but I noticed a module loading scripts in the footer that didn't need to be in the footer.

Do you think it would make sense to add this feature as an option in this module? Or do you think it will cause trouble. As far as I know Javascript and CSS behaves the same whether it's in one file or multiple files.
As websites are used more and more on mobile 3G and wifi networks it really pays to reduce the number of files loaded, so I think this is a good feature.

There are probably edge cases where you do not want this feature, that's why I made a theme setting for it. For instance, while the respond.js polyfill parses stylesheets so fast that it can handle an aggregate file just fine, more advanced scripts like CSS3-MediaQueries-js are slower and might not be able to handle a 200kb CSS file.