Instead of using Evaluate, consider
FindChild. What you can do is pass in a list of properties and a list of values, create arrays of the properties and values, and then use FindChild to find and return your object. The bonus with this is that, if the object is not found, FindChild returns an empty "stub" object with the Exists property set to FALSE so you can still detect whether or not the object exists before you attempt to interact with it.
For the lists of properties and values, you can pass in two delimited strings and use methods like
aqString.GetListItem and the related methods to take the delimited string and parse it out into the individual pieces. That will allow you to target your "FindChild" call to the specific object you're looking for without having to do any major mapping.
Now, you might still want to do some basic mapping of your application and, perhaps, the main forms. But you may not need to map everything, just a basic level and then use FindChild for the specific detail bits.
