To the best of my knowledge there is no way to do this.
A TFRJOB command could cause a current interactive job to start the next routing step in a batch subsystem, but it would generally remain as interactive. There is no connection between what subsystem a job is running in and the job’s job-type (as long as the target subsystem allows the workstation to enter that subsystem.)
Perhaps the routing step <i>could</i> release a device that it was previously associated with, but I don’t know (1) if that would reset the job-type nor (2) what becomes of the display session since no signoff has occurred. A batch job that acquires and later releases a device leaves the device in its original state, e.g., with a normal logon display.
A batch job <b>can</b> change its job-type to become interactive simply by acquiring a display station and opening a display file.