What use case are you trying to solve here, that is what would be most helpful in getting you further help?
One key point, doing the modifications you are doing is going to negate your support, just FYI, any modifications would need to be excluded and things tested with our default setup to see if you can still replicate the issue with the default setup before submitting any future issues to us for investigation. It is best to not modify things if you can avoid it, which is why I am asking about the underlying use case and the reason for the mods in the first place...
Lastly, not all of the settings in the QVWS resource are used when using IIS as well, many of those are just for our QV Web Server, so keep this in mind as well, you may need to be making additional mods in the IIS side of things in this case.
That being said, I think I know where things may be going wrong here and that is where the parent page is in relation to your customized pages.... The paths are relative, so things may not be resolving for that reason I think, but I am not certain. Sorry I do not have something better here.
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.