Integration between Media WYSIWYG and Storage API (have WYSIWYG uploads use an available file scheme rather than just a directory).

Current problem with Media WYSIWYG & Storage API

Currently, I'm able to use Storage API with Media & File Entity by specifying a file scheme to use when editing a file field (e.g. Public, Private or whatever I've defined via Storage API). This is not the case with files added via Media WYSIWYG as there is no way to specify a file scheme for this upload method, only a directory via Media browser settings. Is there a way we could amend this so that Media Browser settings would present the user with available file schemes for WYSIWYG uploads?

Why Storage API

Storage API is the most appealing option I've found for integrating with external file services like S3. There are other options out there that work with Media WYSIWYG but they are dreadfully slow due to uploading directly to S3. Storage API gets round this by using Drupal to handle the initial upload as normal (including creation of required image styles) and then syncs with S3 on the next cron run (amending any paths to files once they are available remotely on S3). Storage API also provides a raft of other benefits in addition to this (redundancy through multiple file services, de-duplication etc) - check it out: https://drupal.org/project/storage_api

This lack of possible integration with Media WYSIWYG is the only thing that keeps stopping me from using it.