Could you please start from the beginning and tell us what you’re doing when you got the exception? It seems that you’re writing some custom code, right? If so, you seem to have a bug there, but we can’t comment on your code unless you share it with us.
Yes, Microsoft.Dynamics.Ax.Frameworks.Controls.ProductConfiguration.InvalidAttributePathException isn’t an X++ class, therefore it’s correct that you don’t see it in AOT. But you’re wrong in thinking that catching an exception requires creating an object. The object is created by code throwing an exception, not the one catching the exception.
You can either catch the specific exception, or all exceptions. For example, this catches all exceptions:
System.Exception ex;
try
{
...
}
catch (ex)
{
...
}