Because cmd.exe running on your local pc reads the contents of your bat file and tries to execute it. When it runs psexec, it in turn runs cmd.exe on the remote pc. The remote cmd.exe tries to read from stdin (console input) and is waiting for you to type something in. The local cmd.exe has no way of knowing that the next line in the bat file (net use) is intended for the remote cmd.exe. It's waiting for psexec.exe to terminate so that it can run the net use statement locally, which is not what you want.
The easiest solution to is to use psexec's -c switch to copy Delprof2.exe.
-c Copy the specified program to the remote system for
execution. If you omit this option the application
must be in the system path on the remote system.
Like this.
psexec \\pcname -c delprof2.exe /ed:(Username)* /d:60 /q /u /ntuserini
If you have multiple commands that you need to execute, you can tell psexec to copy a bat file that can execute the command sequence.