Allow for arguments before binary target

Say I have a binary target chess, which I manually run using ./chess 8 1000 16 2 2 q 0 1 . I can achieve the desired behavior by having a launch configuration like so:

{
            "cwd": "/home/timman2er/Documents/ki-schaken",
            "binaryPath": "/home/timman2er/Documents/ki-schaken/chess",
            "binaryArgs": [
                "8",
                "1000",
                "16",
                "2",
                "2",
                "q",
                "0",
                "1"
            ]
        }

However, in my workflow, I would rather run time ./chess 8 1000 16 2 2 q 0 1, which gives me the time it took to execute as well.
Is there a way to add commands to be put before ./chess 8 1000 16 2 2 q 0 1? I would imagine some users might wanna run val-grind as well in their launch configuration.

If there is a way to do this please tell me. If there isn't, then with some help I should be able to implement this myself.

Start by tracing how the launch configuration uses binaryPath and binaryArgs to construct the executable command. Check how a configurable prefix such as time or val-grind could be represented, then verify that the resulting command runs the prefix before the binary and preserves all binary arguments.