Not really sure what you're after. I have sometimes been able to defeat the compiler optimizer by using an expression on the left-hand side of the equal sign. E.g.,
select * from employees where SSN+0 = 123456789
instead of
select * from employees where SSN = 123456789
will change the execution plan from Index Seek to Index Scan.
I needed to use this in a different DBMS where the optimizer was choosing the wrong index in a complex join. By making it impossible to use the index chosen automatically, I was able to force the compiler to choose a different index that was better. But that DBMS did not have syntax for a compiler hint as to what index to use. SQL Server does.
So again, why do you think you need to do this?