Looking at that model,you can't control "Torque" because the model doesn't include a suitable motor model that characterises the torque per amp of the motor.
If you just want to simply add that, then just use a fixed constant (ignore saturation etc) and assume that the motor makes 100% of that torque constant when the current is 100% in the q axis, and makes 0 % when the current is in the d axis.
ie, assume for your virtual eMachine a value of say 1Nm per Amp in the q axis. If you have 10 amps, all in the q axis, then assume 10Nm, if you have 10 amps total, 5 in q, 5 in d, then the assumed torque is 5Nm etc etc
For a real eMachine, the relationship between current and torque is complex, and control inverters are calibrated on test rigs to determine that characteristic and to map that into the inverter, allowing the end user to demand Torque rather than axis current. That mapping is of course intrinsically bi-directional, so is also used as feedforward to the FoC controller.