“I would like to assume” refers to an assumption OP’s production environment making use of the property, it’s not a statement you’re supposed to agree or disagree with.
On the other hand, the commentary provided is something that warrants commentary.
It’s really not. Refer back to my statement saying that with this property off, sound playback can replicate. It’s as easy as spamming the play method on sounds to produce a crash or unintended audio effects. Relevant exploit report which a former engineer replied that RespectFilteringEnabled was designed to combat against said playback exploits. It’s not just good for combating exploiters either; it has various production uses.
The server can’t see it*
That doesn’t matter. Sounds that already exist in the DataModel can be fetched and played. Exploits aren’t limited to creation, they can also utilise existing items to their advantage.
Or you can just play them from a LocalScript with RespectFilteringEnabled on without the unnecessary trouble of needing to set sound listeners and such every time you want to play a sound locally with that API. It doesn’t fix the initial problem either - sound playback will still replicate if an exploiter decides to call play across sounds. You also need to account for other sounds if your game is “sound heavy”.
Please DM me if you have any further questions, commentary or responses about this. Sound playback is off-topic from the OP, we’re derailing this thread a bit.