You can come at it from the opposite direction and make the Qgis python a system python, which enables using standard Windows installers for the extra packages.
This can be done by creating or modifying the windows registry. Here's an example for python 2.7 distributed with Osgeo4w, installed in a non-standard location:
Windows Registry Editor Version 5.00
I created an experimental o4w register python package to add and remove this registry setting at will. It's not o4w or python version specific and uses the currently active environment to determine the appropriate version number and path values. The code is here and works best on 32bit systems; there are some peculiarities to 64bit registries I haven't figured out how to deal with yet.
register-python does nothing if the system python is the same major version, e.g. you can only have one Python 2.6 at a time. It is perfectly workable to have ArcGIS 10 python 2.6 in the registry at the same time as Qgis python 2.7 though.
If you're using the manual approach and editing the registry directly, you can save the current system python by simply renaming it, running the install programs, and then changing it back. Example:
; rename to: