Let me take a step back and try and explain a bit more about how the database is structured.
There is only one PT3 database, but it contains several tables. Each of these tables is a distinct entity; and some are large and some are small. More importantly for our purposes, some are based on individual hand data, and some are based on session data.
So let me give you a bit of an example. There's one table called holdem_cash_player_statistics. (The complete spec of the database is in the Schema, which you can find on our
documentation page, btw.) Each row in the table contains a whole lot of data. So one row might look something like this (technically everything on the left of the equality is a column header, and everything on the right is a data value, but this way it's easier to read):
id_hand = 5, id_player = 15, id_holecard = 26, id_limit = 1, id_session = 1, position = 0, cnt_players = 6, flg_p_open = true,
flg_p_open_opp = true ...
and so on. But you can see that each row is for an individual hand (in this case hand #5 in the database), and for an individual player (#15). (We can also tell he had pocket kings, on the button, and it was folded to him, from the data I made up for you.)
When a statistic is built in the Holdem Cash Player Statistics sections, the column is built by iterating over every hand in every table that looks only at specific hands. This allows you to add up the MGR * 6 (say it's full ring), and divide by number of players to see how many VPPs you got for that individual hand.
When you go to the Holdem Cash Sessions section though it works differently. It iterates over sessions of hands - it does not go down and iterate over individual hands. In particular it looks (mostly) at the holdem_table_session_summary database table. You can see the schema for the full specs, but it's not large. It contains amt_mgr, but it's the MGR for the whole session - which if you have a changing number of players during the session (which is almost certainly true), you can't actually get an accurate VPP count, which defeats the purpose of your stat.
Now to start actually replying to what you said. When you double click on a session on the Sessions tab, the session gets listed in bold and what happens is that PT3 filters to only hand data from the hands in that session (or sessions if you have multiple sessions selected). This doesn't affect reports that work on whole sessions because of the above discussion. But it does affect reports that use the HCPS section (which is why the general tab's player statistics report will be affected).
The real reason for the above digression though was this: to build the VPP/hand type stuff you want for sessions what you actually need is a new database field in the holdem_table_session_summary area, which would need to actually be built into the database when you import. PT3 doesn't do that, and yes you could build it via SQL yourself but you'd need to keep it up to date as well (though if you did it, it would work just fine in a stat).
I hope that clarifies some things for you.