When build-without-the-bytes is used, forcing no-remote + no-cache is often worse than allowing it to execute remotely. If the file is a source file, then it's better to upload it right away and execute the copy remotely (cached). If the file is an output file, then Bazel has to download the file in order to perform a local copy. Best case scenario, no work is ever done locally, and this breaks that.

It's a better policy to not try to set these at the rule level.

If this needs to be user-configurable on a per-rule basis, it might be viable to create a flag and then set these tags only if the flag is set.