You've left out virtually ALL the details I would use for gameplanning. If you're gameplanning based on team averages, to quote Mr. Mom, "you're doing it wrong." You have to gameplan based on the starters and big-minute backups and where they're playing. I literally never look at team average for DEF or ATH or SPD because I don't care about that. A D3 zone team could have 3 guards with 90 speed, 2 SFs with 60 speed, and 7 posts/walk-ons with an average of 10 speed. That group of players will have a team average of 38 SPD and you'll come out calling them slow. I'd call that team fast. In the slowdown zone you can easily get those guards to play the lion's share of minutes at the 1 and 2 if not all of them, the SFs are quick, and in a D3 zone I really have minimal concern for the speed ratings of the posts. The same applies to athleticism, defense, etc. If 8 or 9 guys get most of the minutes only their ATH ratings matter. Against man in particular you have to look at each individual starter separately and say "this is a guy I can attack" or "this is a guy I need to avoid" and adjust your starters' distro accordingly. And team REB works much the same way as speed - REB in guards is so very unimportant that your zone team's team REB is almost completely irrelevant. If they've got 3 guys with 90+ and decent athleticism and a half-decent rebounding SF they're a good-rebounding zone team, but that doesn't necessarily have to reflect in the team average if they carry a lot of guards or have a walk-on or 2. But listing team average LP is really the most silly. One guy with 90+ LP is a dominant inside scorer. Two guys with 60 are solid. A whole team of guys with 40 will need some guards with speed, ATH, and BH or a lot of PER to score but might have a much higher team average.
Finally, while you did say "with your respective teams in mind," but a lot of us have more than one team and gameplanning is extraordinarily team specific. It's also highly system specific.