Retrieval of Generalisation Entity shouldnt retrieve properties from Specializations to optimize performance

As layed out in this question as well, Mendix unnecessarily retrieves all attributes and associations of specializations from the database when only a retrieve of the Generalization is modeled. See below example, the single retrieve causes SQL queries to every specialization table, while this is not needed.

The only benefit is that the activity 'Cast to specialization' can be done without any database interaction, but now a lot of extra (unrequested) effort is done for 'just' the retrieval of the generalization, which is in my opinion an overkill.

For performance reasons, I would rather see that Mendix:

• does not retrieve further specializations than requested in the model;
• enables filtering on specialization type (submetaobjectname is already a property)
• enables casting lists of objects (which uses database interaction)

I know this is also done for association tables, but these belong logically to the owning object which you retrieve up until that level of specialization.

BTW: The example above would explode in number of queries if every specialization also has multiple associations.