I'd first challenge your impression of SNAC. It is not there to restrict WiFi when a wired ethernet connection is used (you can accomplish this with just SEP's Location Awareness and FW policy alone).
SNAC is used to make sure that devices connectiing into your network meet your minimum security requirements. These requirements can be based on patches, installed security software, age of installed defs, any many other factors.
Because it's there to help protect your general network (and by extention, everything connected to it), it's equally applicable to both workstations and laptops. The only difference being that laptops are more likely to fail your requirements.
As far as side effects go, this depends entirely on what you configure as a "Host Integratiry Failed" action.
If there's no followup action set, then there's no side effects really. SNAC will just report on which endpoints have failed what requirement.
If there is a remediation action (i.e.to install a patch/software if it is not already present), then it should be equally relevant for both workstations and laptops.
If you have configured blocking, then you will need to consider how this would affect your users (both workstations and laptops), and if the inconvenience to the workstation users outweighs the risk to your network. If it does, then separate out the workstations from the laptops so they behave differently.