Okay @Valki I am going to reply to part 1 of your post there to take the "this is how I would respond to you should you make this discussion" road.
In regards to the Aeon t1 pd hit box issue while under construction, let us say it is an issue for simplicity (I did not watch the replay yet - sorry!). This issue would be communicated to the devs/game code manager @keyser and his team. I would not mind doing it initially, but my preferred method would be to also introduce you to HOW the issues are managed.
To understand that, you must at least in some way know project management for software engineering and for that I give you the "FAF Github Repository:"
For this particular issue, it likely would fall under "fa" which stand for Forged Alliance Game Lua Code. It might be more of a "hitbox / model issue," but less us assume it is a code issue for now. To address this, you must make a report here:
So, Valki, next time you find this issue, you can log it there, and it will be reviewed by someone on the team.
IMPORTANT: we have maybe 7 TOTAL software-capable workers on FAF, and of which that is maybe 1-2 people for the Forged Alliance Game code. If you look at the "issues log" here: https://github.com/FAForever/fa/issues you will notice there are in current as of my writing 348 other issues.
So, yes, I would discuss with you how to get this issues noticed and fixed properly rather the message board, but also ask you understand that the 1-2 people working on the game LUA code are quite busy, doing this for free, and therefore it will take quite some time.
I hope that helps answer you in how I would engage with yourself and others about the issues, hope it is to your and others' liking.
For the second part, will get to that later. I am heading off to dinner now and to watch a nice game of ice canes warriors battling to get a giant, silver bowl with names inscribed on it.