Meetings on a Topic

It seems unlikely. Perhaps it would be better to time-box the meeting to begin with, and accrue empirical evidence about whether or not the problem is actually solved.

Instead of thinking about the vague concept of "good idea", it would be better to think about things like if capturing this information would be valuable, how the value compares to the time and effort to collect and format, who would be receiving it, and how they intend to use it.

Personally, I don't see the value in collecting this data and any time or effort spent would not be worth it, so I couldn't consider it a good idea. But your environment and context may be different.

I agree with @Ian and @Thomas.  Since all of the things you list are part of "doing the job" to deliver software, I see little value in gathering that data.  Would you consider gathering the number of times an individual used the backspace or delete key on their keyboard?  I doubt that would be a useful metric to gather.  The ones you mention seem just as unuseful to me. 

Also, why would you gather any individual metrics when the Scrum framework is built around a Scrum Team?  The team is striving to deliver usable increments of value each Sprint.  Any metric you gather should be focused on the team and not the individuals.