Concern that this input stuttering issue may not be visible internally

I would like to express a concern regarding this keyboard and mouse stuttering issue, not as a complaint, but because it genuinely feels like this problem may not be sufficiently visible internally at EA or DICE. After extensive testing and communication with other affected players, it has been confirmed that multiple users are experiencing the same behavior. Based on collective testing, the issue appears to be directly related to the Javelin anti-cheat and its interaction with input handling. For affected players, the impact is severe. The stuttering is triggered by keyboard input while moving the mouse, the specific keys affected can change on every game launch, and restarting the game or rebooting the system may temporarily resolve the issue, but it can worsen over time until the game becomes unplayable. It is important to clarify that all commonly suggested troubleshooting steps have already been tested and ruled out by multiple users, including closing Steam Friends and Steam overlays, closing MSI Afterburner and RTSS, uninstalling or disabling all RGB and hardware control software, removing motherboard utilities, disabling all overlays, testing different keyboards and mice, testing different USB ports and polling rates, and performing clean driver installations. None of these actions resolve the issue. What makes this situation particularly concerning is that the issue appears to affect only a relatively small subset of players, which raises concern that it may not be receiving sufficient attention internally despite the significant gameplay impact for those affected. At this time, it is unclear whether this issue is known internally, formally tracked, or currently under investigation. I would like to ask if there is a recommended way to ensure this issue is properly escalated or if there is any specific diagnostic information that affected players can provide to assist in identifying the root cause. Several players across forums and Reddit have independently described the same behavior, suggesting this is not an isolated case. Any clarification or guidance would be greatly appreciated.