Hi Oleg,
I understand wanting to prevent bad content. Do you have workflows setup to review/approve Topics before they become live? The method you describe sounds like you are taking an audit approach. That could be time prohibitive depending on the workload and bad content could more easily slip through.
To answer your original bcf question, the only way your requirements may work is if Topics are only bursted with a Map. Then you could use some XPath to get the parent Map title a the Topic element. If a Topic is already bursted into WC or the Topic is bursted separate from the Map, this won't be possible without some heavy customization.
The better approach would be to save content based on context of the content rather than the referenced material. References are dynamic and can change and cannot be reliably used over time. Proper workflows to keep the content clean are also a best practice.
You might reconsider your content model a bit before attempting to code a solution that doesn't really get you want you want.