The data under the Log-ReportStatistics class does not include the active application or access group, but it does include the active operator id. You can use class joins to add these if you like. Using the Report Definition pyReportUsageByUser as an example:
Under the query tab:
Under the Data Access tab:
The conditions for the OP class join:
The conditions for the AG class join:
Each added class join will degrade the performance of the report, so use them wisely. You can always group by access group name instead of application and only use the OP class join with OP.pyAccessGroup as your added grouping column.
Ah, I see the report now. It appears to be the List View StandardLicenseCompliance.
It looks like the data backing that report is summarized in a way that it loses information on user, application, and access group. However, it appears to be a summary of other available data. Each row in the table for class Log-License-Usage-Hourly describes the number of invocations per user per application. I'm not sure how users are divided between "regular" and "occasional", but you can try building your own report from this data.
Try creating a Report Definition that applies to Log-License-Usage-Hourly with the following columns:
Here are all the columns I'm seeing on that class that you can use to add more detail to the report: