For transparency, here is a non-exhaustive list of reasons why this plugin cannot switch to using the "Pro" API completely even though the "Classic" API is being removed soon.
TLDR: The replacement "Pro" API is still missing essential features over 5 years since it was started.
No obvious way to view the command history for a specific device. The classic API had "/mobiledevicehistory". The Pro API has no specific endpoint for it and no section. If I should use "/v2/mdm/commands", it returns a 400 error with the default params from the Swagger UI with absolutely no details of what the error is. If I should use "/v1/mdm/commands", it is obtuse. I am forced to know the UUIDs of the commands already or the management ID of the device (I presume). I cannot get the management ID of the device unless I first make an API request to get the entire mobile device record at /v2/mobile-devices/{id}/detail. Surely there is already only one management ID per device, so the "/v2/mdm/commands" could accept a UDID, accept a type and ID (mobile device/computer), or be split into two (one for computers and one for mobile devices).
No way to get the permissions of a specific account. The classic API had "/accounts/userid/{id}".
In addition to the previous point, there is no way to get a list of Jamf accounts at all.
There are other annoyances with the new API, but they can be worked around. In some cases, it may affect performance.
For transparency, here is a non-exhaustive list of reasons why this plugin cannot switch to using the "Pro" API completely even though the "Classic" API is being removed soon.
TLDR: The replacement "Pro" API is still missing essential features over 5 years since it was started.
There are other annoyances with the new API, but they can be worked around. In some cases, it may affect performance.