RESP endpoint commands don't require previous value

The SET command doesn't require a previous value. Therefore we should use a cache that has SKIP_CACHE_LOAD to prevent reading from any persistent storage when doing the write as it will be unnecessary and adds additional latency.

There may be other commands, and we should probably ensure HR does the same check for its command when it is ignoring return values.