Allow user to define destination on drush features-update

The title here is probably deceivingly simple. The end goal here is to be able to do something like 'drush @[alias] features-update [feature-name] [local destination]' where the alias is a remote installation. Unless I'm missing something, this would make pulling changes down from a remote server to a sandbox to commit much easier than using the Features UI module. This is especially important in situations when the developer doesn't have write permissions on the remote server as such is the case with Pantheon.

Anyone aware of any challenges we might face trying to accomplish this?