No, sorry, it doesn't fit with the internal design.
If you're only requiring one-way traffic (always to Destination), you can use Fast Backup to avoid scanning the Destination, but this must only be used for a Destination (the branch, not 'the device') that is not modified by any other person or process (including any another profile, whether Fast Backup or not). Otherwise, you can lose data if what the FB profile thinks is there isn't the case.
Naturally, you can't do this for Sync (2-way file traffic) - if potential new/changed files might be on either side, you have to scan both sides to find them.
The Help has lots of background on Fast Backup, as does the KB
If you're only requiring one-way traffic (always to Destination), you can use Fast Backup to avoid scanning the Destination, but this must only be used for a Destination (the branch, not 'the device') that is not modified by any other person or process (including any another profile, whether Fast Backup or not). Otherwise, you can lose data if what the FB profile thinks is there isn't the case.
Naturally, you can't do this for Sync (2-way file traffic) - if potential new/changed files might be on either side, you have to scan both sides to find them.
The Help has lots of background on Fast Backup, as does the KB