SELECT query types and optimization
None of the above.

A "full scan" is irrelevant if the table has only 10 rows.  Ditto for "not using an index".

There are many queries for which no index is useful; you stats will have you stumbling over them.  For example, if you index a 'flag' (yes/no, M/F, etc), the optimizer will usually eschew the index and simply scan the table -- because it is more efficient to do so.

"First table".  Unless you are looking at the EXPLAIN, it is difficult to predict which table will be looked at "first".  Even the existence of LEFT does not conclusively predict ordering of the tables.

What is your goal, anyway?  The main goal, in my opinion, is to find and fix queries that are bogging down the system.  To that end, I want a list of queries, ordered by total elapsed time (number of occurrences times avg time).  An that is very efficiently provided by

long_query_time = 1
turn on slowlog
wait a day
use one of these to get the list:
    mysqldumpslow -s t
    pt-query-digest


Then, I get EXPLAIN and SHOW CREATE TABLE for the first couple of queries and work on them.

If you want to see 'change over time', then record the 'total time' for the worst queries and see it those get better or worse next month.

You may find that some of the worst queries are not SELECTs.