Might be.
A plug-in most certainly could interrogate MC re. track information and provide some stats. If this is important to you, I can suggest ways that you can get what you want now (rather than waiting for some enterprising plug-in developer to implement such a plug-in).
Not to be argumentative, but rather just explaining why what seems trivial is a little more effort...
MC's database is driven by the files in the library, so current stats are also essentially file-based. For audio, a file is a track. The MC database isn't a relational database, so relational database tables like Albums, Artists, etc. don't exist. Thus, MC would have to calculate extra information by examining every track.
Number of plays for an audio track is easy - MC just updates that track's [Number Plays] field. But Artists, well that would require MC to query the database of all tracks, asking for all tracks for the given artist, and do some counting. Likewise, Albums for album stats, etc.
What would it mean if you have an album where 5 of 10 tracks are played 7 times, but the remaining tracks only played twice? Is that an Album Played of 0 times, or 7 times, or some weighted average of the track played times?