Из общения с поддержкой Microsoft

[EVGL]

Та-дам! Пришел окончательный ответ:

Цитата:

I received the feedback from our Sustained Engineering department that unfortunately the fix that has been made for the reported issues 1-3 can’t be delivered as a hotfix because it’s a hybrid fix (changes has been made in both application and kernel code). We only have Service packs or next major releases as shipping vehicle for such type of fixes. For this reason this issue will be resolved in Dynamics 4.0 SP3.
About the performance issue (issue 4); it’s absolutely true that the form opens significantly slower in Dynamics AX 4.0 compared to Dynamics AX 3.0 because of the change of design that was done to incorporate VCS systems into it.

When Dynamics AX 4.0 form is opened, it gathers information from all the sources where the given object is present. In particular, it creates a TreeNode object for the instance of object on each of the layers, and this can take some time, especially if an object is big and modified on many layers (including many layers in the application in the Old folder). In Dynamics AX 3.0 this only happened when layers were actually compared, so the form could be opened quickly.

It should be possible to increase performance by introducing a change that would delay these operations till the time when they're really needed but this is a design change that can only be done in a next mayor release. For this reason it will not be resolved in a hotfix. As a workaround it can help to delete the old application if it's present to improve performance.
I know this is not the conclusion that you expected but I hope you understand why we can’t provide a hotfix for these issues at this time but need to delay it for the next service pack (issue 1-3) or future release (issue 4).

Что же, буду ждать.