The /stopsound command (/stopsound @a) does not mute all sounds correctly when hooked up to a 20Hz clock (blue repeating commandblock)

Taken into account that 20Hz does not suffice to mute all sounds constantly, some sounds are not cut off at all. Sometimes the sound of fire for example keeps running for longer than a tick or 2 ticks, quite a long sound can play fully without getting cut off...

Expected:

• Sounds will play for max 1 tick cause /stopsound @a will cut it off then

In Practice:

• Sometimes sounds just fully keep playing.

Possible solution/fix (idea):

• Have data values on each player that keeps track of which sounds have been muted in that tick, the next tick, that datavalues get wiped if /stopsound is not ran that tick, and keep the datavalues/change it, when it is ran.
  You may have something like (some messy pseudo-data)

  {
    "muted": [
      "music",
      "ambient",
      "hostile": [
        "mobs.zombie.hurt"
      ]
    ]
  }
  

Where you would have a list of all the sound categories that are muted, and a list of specific sounds under a category. if all sounds are muted, either a list of all of them, or something else is in the data? idk
it is an idea for a fix.

The result that you want is complete silence when /stopsound @a is ran each tick.
and completely specific muted sounds with /stopsound @a <category> <sound>