I had a similar experience. I learned Java first, then C#. For a while I was working with both languages. I had a situation occur with a project in each language that required reading and writing XML. I spent two weeks researching (and experimenting with) the multiple libraries for XML processing in Java before I found one that best fit my needs. In C#, there were only two choices (one for processing the entire DOM and one for streaming) and making the choice was obvious. The issue was that there were hundreds of Java libraries from multiple sources but only the Microsoft official libraries for C#. This was over two decades ago. Things have changed. Research is more efficient. Both languages have matured and are more stable.

Lard no!

First step is to answer the question, "Why are you tracking the stats in the first place? What purpose does it serve?" The answer to that question should guide you, since the next question would be, "How can I achieve that goal or purpose better?" So, for example, if you are tracking statistics so you can motivate the player to keep playing by making their progress visible, then you want to track and show the statistics to maximize that motivation. You also want to reward the player as often as you can to keep the player motivated. In this case, I would track and report each stat separately and I would have a "best overall" generated using the following algorithm. The first game played generates a time = X, turns = Y, and score = Z. This becomes the "best overall" game. Only when a game results in two of these values being equal(or lower) and one being lower would you create a new "best overall game". This means a player could improve one of the stats(and be rewarded for it), but would not get a new best overall award if they did so at the expense of one or more of the other stats.

Carpet Diem -- today the carpet, tomorrow the bed covers.