Sergey,
I know it's a rather long shot, but a solution may be to generate the proxy assembly at design time using a custom tool and then instruct NH to use the proxies from a given dll using a custom naming policy.
Eg. when a proxy is needed for
Code:
MyNamespace.MyEntity, MyNamespace
automatically search for proxy
Code:
NHProxy.MyNamespace.MyEntity_NHProxy from NHProxy.MyNamespace assembly
Another idea would be to create a tool that takes as input a set of DLLs and that creates the proxies automatically, and this tool can than be use with setups.
What do you think, does this deserve any attention ?