Sure, but then we would need to coordinate a change in oem-vagrant in the overlay and this patch. There's no reason someone couldn't completely bypass this code and want to set up the environment themselves. I think it makes sense to leave the initial path /var/lib/coreos-vagrant/user-data along, but to find a better name for the daisy-chained user-data file at /var/lib/coreos-vagrant/actual-user-data