In this case the (admittedly minor) impact of the compare instruction would counteract the intended speed gain and with inlining you'd add some additional flash usage for the instruction which will never be called each time you'd use one of these macros (I guess, since I doubt that the optimizer will kill the respective branch).
I'd rather turn that logic round and implement the set/reset functions a priori and use these in a third function or macro depending on the value - as pointed out in @mdma's macro.