There is no built-in method to execute a command or play a sound for all recognized commands, only unrecognized phrases.
For the latter you'll want to assign a command to the "Execute a command each time a phrase is unrecognized" option.
If you want recognized commands to play a sound, you'll have to add a "Play a Sound" action to each individual command.
In theory you could use some of the tokens to build such a system, but it comes with serious limitations.
The basic setup consists of two commands; One to set a flag that determines whether the command is unrecognized, and one that continuously runs in the background to monitor the command counter and play sounds depending on the status of the unrecognized flag.
Command Recognition Checker
Begin Decimal Compare : [>lastCommandCount] Has Not Been Set
Set decimal [>lastCommandCount] value to the converted value of {CMDCOUNT}
End Condition
Start Loop While : [1] Equals [1]
Begin Text Compare : [{EXP: {DEC:>lastCommandCount} = {CMDCOUNT}}] Equals '0'
Pause 0,01 seconds
Begin Boolean Compare : [Unrecognized] Equals True
Set Boolean [Unrecognized] to False
Say, 'Unrecognized'
Else
Say, 'Recognized'
End Condition
Set decimal [>lastCommandCount] value to the converted value of {CMDCOUNT}
End Condition
End Loop
Make sure to check the "Allow other commands to execute while this one is running" option is checked.
Assign this command to the "Execute a command each time this profile is loaded" option.
Unrecognized (voice disabled)
Set Boolean [Unrecognized] to True
Assign this command to the "Execute a command each time a phrase is unrecognized" option.
Note that the "Command Recognition Checker" command loop has a 10ms delay before checking the unrecognized flag, this is to avoid a race condition where the flag-setting command finishes executing after the "{CMDCOUNT}" token has already been implemented, and after the loop in the "Command Recognition Checker" command has already come around.
Main limitations: This will make a sound for each command, regardless of execution method. E.G. if you trigger a command with the keyboard, it'll still make a sound.
Using a "Stop all Commands" action, or equivalent, will stop the monitor command and sounds will no longer play.
You could use the "{SPOKENCMD:}" token to try and work around the former, and to use a plugin or inline function to circumvent the latter, but it's an imperfect solution regardless.