For the time being, if you've successfully overcome this issue by redesigning your solution, then I'd recommend going with it...
The CLR team may be addressing this currently unsupported functionality in the future. It would be a useful addition to strong name generation: deriving the strong name of any assembly - whether it was signed or not - to be used in cases where there is no signer
and where no revision control is needed (as is true in this case where the assembly is dynamically generated).
Thanks for sharing your problem. Sorry the solution was so abstruse.