WinRT: Difficulties to control the contents of the final .appx package

Deploying a fresh application works out-of-the-box, which is great. But when I try to tailor the content of the resulting .appx package, it gets a bit hairy. I assume that not all issues are due to winrtrunner, but also to qmake and windeployqt.

1. The package contains QtWidgets by default, even if there are no dependencies on it. Adding WINDEPLOYQT_OPTIONS = --no-widgets to the .pro file does not have any effect. Only the parameters from the "Run windeployqt" deplyment step in Qt Creator are passed to the windeployqt call, which I found irritating.
2. No parameter for windeployqt seems to be able to disable the shipment of "QtNetwork", "imageformats/" and "qmltooling/".
3. All the "plugins.qmltypes" files get included, although they are of no use on a mobile device. (only Qt Creator uses them)
4. WinRT seems to have a mechanism to provide an icon for differnt DPIs. One icon can consist of these files: "foo.scale-100.png", "foo.scale-140.png", "foo.scale-240.png". The app manifest would reference it just by "foo.png" and all three versions would be packaged. But the "WINRT_MANIFEST.logo_*" fields do not seem to support that magic, they want a full file name of one existing .png file.

I did not find a winrt equivalent of "ANDROID_DEPLOYMENT_DEPENDENCIES". That would shut off windeployqt, and I could manually hand-pick what I need. And most of the issues above would be solvable.

Having the possibility to provide an own "AppxManifest.map" would be even cooler. But I have not found a way to force the deployment to use my own "AppxManifest.map" file. Is there a way?