That requirement feels quite strange and in my opinion it points to a problem in your content architecture.
In AEM languages are normally organized in sibling folders which helps you to build navigation and ease the permission model.
Also the MSM is not designed to rollout 2 blueprints into a single folder. While it might work on the first rollout, please check the behavior when it comes to duplicate page names and changes there. I would even go that far and say that this scenario is not supported, because it deviates quite a lot from the documentation.