That script was flawed from the beginning. You can’t rely on it for everything. Use it to get ideas as to what “may” be a potential areas for improvement, but don’t expect more. For example, some distros want you to add a group for real time limits and memlock, and then add yourself to that group. Some distros use “Audio” as the name for the real time group. Other distros use “Realtime” as the name for the group. Pipewire recommends a group named “Pipewire”. Some distros don’t give an assigned name, and you are expected to define your own group name and assign your limits and memlock to that.
Unless things have changed, I believe rtcqs looks for a group called, “Audio”. That means that it will fail that check if the group in your distro is named anything other than “Audio”. With 600+ distros available, it is highly unlikely that the script could catch every realtime group name, even if the developer tried to add the most common names.
I’m sure there are other possible problems with the script, but that is the one that I am most aware of. A developer can only do so much within the commonly changing world of Linux. That’s why I say use it for suggesting tuning possibilities, but don’t assume it is the final word on what is right or wrong in your system.