Understanding API's output of dataset/{key}/document and optimizing related API call

I’m currently working with a subset of occurrences and I’m also interested in their related metadata. The endpoint dataset/{key} of the PrincipalMethods Registry API does not return all the information I’m interested in so I’m directly fetching the dataset{key}/document endpoint to get the complete EML in XML format.

The ‘problem’ I’m facing is I also want the information on who published the dataset.
As I experienced it, there is currently no information on the publisher returned from the endpoint dataset{key}/document (is this correct?).

Currently what I’m doing is I fetch the whole EML in XML format, I then query the dataset/{key} endpoint which returns the publishingOrganizationKey and with this I then fetch the endpoint organization/{key} from the PrincipalMethods Registry API and find a way to insert information of the publisher reformatted as a responsibleParty object in the EML.

This results in 3 API calls (one for the whole EML as XML, one for the publishingOrganizationKey, and one for the publisher information) for one dataset.

I have two questions:

1- Would there be a more optimal way (less API calls) to achieve the same end result?
2- In the EML schema 2.2.0, in the dataset element, there is a sub-element(?) for publisher. I’m sure there is a reason why it is not returned in the whole EML as XML from the endpoint dataset/{key}/document, but I’m curious to know why?

Thank you!