sp_who2 ‘active’ shows select that starts at 2147483647cpu time and that blocks itself

I was checking an occurrence of a large number of batch requests from an application and noticed that, while not doing any heavy reading or writing it showed a CPU time of 2147483647 immediately after being started.

like this

enter image description here

I understand that the problem is on the application itself, but I don’t understand why it is showing the 2147483647 CPU time and why the process can be SUSPENDED and RUNNABLE at the same time. Is there any way I can optimize this using just the database since I don’t have access to the application itself