To answer your question:
You could likely create something that tracks this using a custom Region Behavior. Details of RegionBehaviors can be found here: http://msdn.microsoft.com/en-us/library/dd458944.aspx
You'd simply create a dictionary that tracked the region name and the associated control, since you have access to both from a Region Behavior.
If you need access to the control at the time a view is being added to the region, you would want to use a Region Adapter for this purpose (details at the same link above).
However, I agree 150% with Kent here that I smell you are doing something you should not. If you are trying to customize the layout or create animations / etc you should really focus on a strategy that doesn't require you to break the abstraction that Regions give you.
Something as simple as a style w/ data triggers could give you what you are looking for and wouldn't force you to know too much about the container from the code that adds the views to the region.