Ok I have the answer,
In fact in the SecurityProviderTpmHsm class, you create a new endorsement key in the endorsement hierarchy.
But since the endorsement hierarchy has a dedicated seed and the new key template is always the same, we always get the same key when we recreate it.
It's also the same for the TPM_RH_OWNER hierarchy (storage).
So yeah, actually the SDK is using TPM 2.0 specification.
Thank you.