Your Data Collection is Inaccurate Due to Buggy Control Settings

I've watched Episode #2 at twitch and in there you've mentioned that "you're collecting data about heroes first" to determine which heroes need "tuning", not nerfed since you seem to dislike this word. And when I knew that the next patch is "early October" the first thing that struck into my mind was the title of this post exactly as I assumed you'd patch the controls quickly enough in the second week.

First of all, I'm talking about the sensitivity and also aim assist on "console". There is a bug where the sensitivity settings "do not apply" or "do not do much". The Aim Assist also cannot be turned off completely. Turning around is a difficult task in PvZ BFN as the sensitivity is too low. However, I'm aware that it's a "bug" and not by design. If you try buying a capsule from Reward-O-Tron and then try to move the right analog stick after having your sensitivity cranked to max previously, you'll notice that you can turn way much faster as intended like GW1/GW2. Sprinting after buying a capsule resets the sensitivity back to default and ignores your settings. There is another issues where the game limits your frame rate on PS4 to 30 FPS after going back to hub. This results in a noticeable input lag.

Also, for some reason, Nightcap has the easiest aim settings in the game internally. Landing shots as Nightcap is almost guaranteed on a console, unlike playing as other heroes.

What that all means is, since players cannot perform as good due to control restrictions/issues which translates to the players not performing at their best true skill level, the data you are collecting can be rendered invalid and inaccurate. The "balancing" your are most likely considering might not be accurate and might result in issues after the aim settings are fixed.

What you should have done for the second week was, releasing a patch to fix those issues first.