Logins are hard to capture in auditing because of their very different natures, and by default you can really only capture local, password-based logins, but not SSO-based authentication. I myself had to implement a custom module to audit user login times when a customer needed that for their Enterprise license management.
Logout times will be even harder to next to impossible to audit - most of the time, users do not actively log out, instead letting their session expire after times of inactivity or by closing their browser. This cannot be audited at all. Even the active logout in Alfresco Share cannot be audited, as it is an action that does not reach the backend (where auditing takes place), and only actively destroys the session in the frontend (Share).
Furthermore, with auditing you will not be able to record any (logical) activities on the Alfresco Share fontend (or Alfresco Content Applications), as auditing happens in the backend - you will only ever be able to audit low-level actions like "read-access to node X" without knowing the context to that access, e.g. whether it was part of a navigation action or because the user wanted to look at the metadata details.
Similarly, you cannot differentiate the read access to a PDF's content in Alfresco auditing between the use cases of "preview in PDF.js within the UI" and "download to local disk" - they look the completely same.
Lastly, the aggregation of many small audit events into a summary as shown in your requirements screenshots is a very tall order. It can be possible with custom auditing (out-of-the-box alfresco-access / alfresco-api will not be enough), but will take quite some effort. Also note that you will likely have to create multiple audit applications in a two-tiered approach - first tier is about collecting all the low-level audit events about individual actions / events, while the second tier will have to use scheduled jobs to aggregate the first tier entries into higher-level summary entries.