The more analytics data you collect, the more data there is to wade through. This isn't necessarily a problem in and of itself if you know how to sift through the large quantity of data and pull actionable insights from it (i.e. visualization, querying and drilling down through the data, summarizing the data with pivot tables, etc.), however having too much data can present performance problems.
With GA, you don't necessarily need to worry about the performance of your analytics software directly, since it's Google's servers that are doing the data collection and running the data analyses. However, the free edition of GA has some limitations (naturally):
Events Per Session Limit
In addition to general collection limits and quotas, the following
limit applies to event tracking in ga.js:
- The first 10 event hits sent to Google Analytics are tracked immediately, thereafter tracking is rate limited to one event hit per
As the number of events in a session approaches the collection limit,
additional events might not be tracked. For this reason, you should:
- avoid scripting a video to send an event for every second played and other highly repetitive event triggers
- avoid excessive mouse movement tracking
- avoid time-lapse mechanisms that generate high event counts
Source: Event Tracking - Web Tracking (ga.js) - Google Analytics — Google Developers
Now, if your client/employer is paying $150k/year for Google Analytics Premium, then you'll have a higher collection quota as well as being able to exceed the GA reporting API request quota of 10k requests per profile per day & 10 concurrent requests per profile.
But overall, I think you should be alright with the custom events you have listed. Even combined, they shouldn't exceed 1 event per second.
Edit: Prasad provides this link, which has much better info on the data collection quotas, including a 500 event limit per session as he mentioned.