Quota VS custom VM sizing in service dialog

Hi. I have a service dialog for provisioning 1 vm on vmware with small/medium/etc… sizing option:

I have json definition of sizing hidden under option values:

which is parsed in CatalogItemInitialization to :number_of_sockets, :cores_per_socket, :vm_memory.

But now I came to play with tenant quota - it seems to me that System / CommonMethods / QuotaMethods / requested is being launched before Service / Provisioning / StateMachines / Methods / CatalogItemInitialization therefore my sizing values are not correctly processed.
Predefined catalog item Request info values are taken in account instead:

Am I doing it all wrong? Is there an elegant way, how to make it right? I’d like to avoid the same parsing logic in requested method as in CatalogItemInitialization