I’m similar to @arw2015.
Regarding learning to code, I don’t track my time. I track my progress against a set of concrete, prioritized, micro-goals that I suspect will lead to the accomplishment of my main goal.
Time to completion is not important unless my employer, or the market, is signaling there is a deadline to accomplish something to stay alive as a frontend developer.
I do plan my time spent doing everything else (sports, housework, reading, events) to make sure that I’m regularly setting aside time to learn software development. I would track my working time if I were a freelancer.
For learning to code, it doesn’t make sense for me to track my time reading vs. coding vs. doing tutorials. Instead, I test myself by regularly trying to build things that require me to use what I’m teaching myself. Of course, the ultimate test is getting a real ticket from a paying client and getting it done with as little handholding as possible. That’s getting tracked by Jira, my colleagues, and me.
Finally, in my opinion, the metrics those plugins reports are vanity metrics by themselves. If you’re going to track something, make sure it’s worth tracking by making sure it’s closely aligned with some valuable outcome.