Hey, this seems harmless.
Seriously, don’t SET DEADLOCK_PRIORITY HIGH.
Even setting it to low can be a bad idea. I’ve heard people say, “Well, I’ve got a big process that runs nightly, but if it gets in anybody’s way, I would rather just kill my process than slow someone else down.” Keep in mind that SQL Server is still doing all that work until it hits the deadlock – and if we’re talking about an hours-long process, there can still be hours of work involved in rolling back your process to let someone else win the deadlock.
When you find yourself going near the DEADLOCK_PRIORITY option, take a step back and question every decision that brought you to this point.