Linked Server stops responding for particular login
Stop restarting SQL Server. Just stop doing that. If you have a particular problem with a particular process that is being killed and rolling back, let it finish. Then, find out what's causing that to happen. Use Extended Events, or a server-side trace, heck, even a third party tool like sp_WhoIsActive. Do something.

SQL Server has a transaction log. All modifications go in there. When these are committed, the changes go into the data file. When they are killed, they have to roll back. 

That's just how it works. The rollback has to finish for the database to remain transactionally consistent.

Restarting SQL Server does not make this go faster. In fact, you could easily make things worse, possibly even taking the database offline or corrupting it.

Admittedly, this answer does not address your question, but there's not enough space in the comments to explain why you need to figure out what's causing the killed processes. It could be a DBA, it could be an automated process.

Bottom line: let SQL Server finish what it's doing. If it takes a long time to do something, killing the task will take just as long, if not longer, as that to roll back.