Token with parameters in run scripts broken

Does anyone know of a reason why or a way to fix tokens with parameters failing? There seem to be a number of problems with how they 'work' at this point.

1. They seem to fail silently when using anything but an integer as a parameter, nothing gets returned.
2. They seem to fail loudly when using an integer parameter, in two ways

• If the parameter is expecting a non-integer type, eg uniqueidentifier, it throws a fail to cast sql error.
• If the parameter is expecting an integer, it throws "Incorrect syntax near '0'." which is the same as if the replacement never replaced the parameter object.

REM %NIC1IPGATEWAY%

Using the %NIC{0}IPGATEWAY% example given in the token itself fails, and it is a built in token as part of 7.5.

Anyone have any ideas?