I clearly said they need to hire someone who can communicate with brass at FD also.
It's a two- way deal.
Then you go on to assert that a communicator probably doesn't have enough industry knowledge to effectively communicate. I don't remember suggesting that a rank ameteur coder be hired as a communicator.
And I clearly stated that "gatekeeper middleman at best", which is exactly what you describe - someone as a go-between for the community and the brass as FD.
The problem with information disseminated via 3rd parties is that it will nearly always be stripped down and minimised (perhaps accidentally, sometimes deliberately, sometimes just because they don't understand what they are attempting to relay), losing so much vital information in the process. The only way to prevent the loss of information by going via a middleman is to simply repeat the information provided to said middleman completely verbatim - in which case why not cut out the middleman and simply get the designer/tester/architect to explain it to us directly?
The only reason to have a middleman would be to ask the questions of the relevant people, whether that's asking them to write a devblog on a particular topic, create and participate in a focused feedback thread, dragging them onto a livestream or even just doing a 10 minute interview with them, but any added filtering or information loss by the middleman would be counterproductive. Either way, it wouldn't be the community manager communicating with us, it would be getting the developers to communicate with us.