A lot of your questions about the definition of Conueries can be answered in the kbase:
Basically, it's good to keep your ration of queries per connection high. That is, the more information you can extract from your database with a single connection the better. The reason being is that connecting to your database is considered "expensive" on resources. Once connected, however, queries are generally cheap on resources provided your database is in good order.
If you're editing your templates and database through some sort of web interface then I'd imagine that your hits will be added to your database usage. There's no way I can see that the usage program can differenciate between an Administrator administrating a database through system x and a user accessing a few records through portal y.