Just to have some fun mixing metaphors...

What if the DBAs at the diner ORDERed BUY the Jerk Chicken?  Does it FETCH NEXT itself?
Who CURSORs as a RESULT...

As executing such a set of SQL does NOT produce a result set, the setting should probably be NONE.

Honestly, a checksum value of only 64 bits for 4,000 bytes just isn't realistic or practical.   What is the business case for the checksum value?

And what, exactly, pray tell, did you then do with that glyph ?   Other users will likely want to know...

Now that I've looked that up, I'm thinking that your varchar(4000) column might be a pain point.   Any row with a couple thousand bytes in it is trouble for hashing...

Are you sure that the results of HASHBYTES will never exceed VARBINARY(32) ?   I've never used that function, so I have no idea what it does or how it works,...

You need to anally check to be sure that your method of calculation of CHECKSUM is 100% identical in both environments, and that the data is 100% identical as well. ...

This would be a really good reason to create a stored procedure, which can be easily paremeterized, and from within SSRS.

You're looking for a "file watcher".   Even a simple batch file can do that, using VBScript.   SQL Agent can be the scheduling methodology.
I'll leave the details of looking up...

Mu gut says the Switch function requires each "condition" to be either "singular", or that it be enclosed in parentheses.  just using AND between the conditions needed is apparently not...