I think this answer is ridiculous. I've got a similar situation, but mine is a mature project to which I've just added a second .NET assembly. The second assembly is genuinely secondary, and I'd like my existing introduction to remain the default page for the help, but now I have to re-author it using a different toolset, rework the text and the links to make it apply as an "overall" intro instead of an intro for my primary assembly, because you have not given me control over the default page?
I suppose I could make a vestigial intro that everyone would have to click through to get to the real intro, but that would be stupid as well.