EnterpriseProcessing license would be pulled when your user sends a process to the task agent to be processed impersonated as them. If your user does not have a default license active, then the EnterpriseProcessing license would be counted.
Honestly, I don’t think this would happen very often for us where a task runs long enough to be reflected in the license counts when it is polled, but for a complete picture, you would have to include it.
The function I provided filters out expired sessions. Expired sessions should not be included in the license count returned by AdminLicensingSvc.GetLicense. If you need that information for whatever you are tracking, then modify the function to include them. I do like the idea of recording the session ID as well. Sounds like it would be good to have for what you are trying to diagnose.
At the end of the day, if it’s off by one or two users, I’m ok with that for my purposes. It’s really just to show the trend over time. This reporting was critical when I identified the problem with Elevated License Usage Between Version 2023.2.25 and 2023.2.26 last year