Separate Materialized View reads from Client reads in cfstats

When running nodetool cfstats on a table that is read once a month via DevCenter, the read counts are reporting plenty of reads.

However, because there exists a Materialized View on this table, I am assuming that the internal reads that populate the MV are causing the high read counts.

Could we separate the read counts by client read counts and materialized view counts?

Even better, it'd be nice to know if we could separate coordinator reads from local reads, if at all possible. This would let operators know when TokenAwarePolicies, or IN queries, are being used.

Thanks!