“Best practice” is a fuzzy term that can mean just about anything. For me, the advice for “how to do this” is to avoid using caching unless it is absolutely necessary.
Might I ask why service caching is being used? Hopefully, metrics were gathered and it was determined that response time was such that optimization was necessary and that caching was the way to go. I ask because most of the time I see when caching is discovered (typically by those new to wM IS) people want to try to use it right away – but doing so is usually premature.
The 3 rules of optimization:
2. Don’t yet.
3. Profile before optimizing and optimize only what you need.
Service caching is optimization. For most integrations, it is not useful.
My guess is that people want a way to change the cache expiry time for a service “on-demand” or flush the cache because it is sometimes not returning the desired data (data behind the service changed, but the caching is hiding it). This is the main problem with caching and is why it is to be avoided unless absolutely necessary.
I would strongly advise against using those services to change the properties of a service. Instead, edit the service and re-deploy.