I might not want to do that. I think the current way is a good way. I would want to give access to config and only provide Redis to those websites which can take its advantage.
In future we will be seeing NodeJs applications and possibly other popular programming languages as well. Redis is awesome for most PHP based CMSes as there are plugins. But NodeJS is a different baby altogether. I think the current implementation is taking that into account as well. NodeJS based apps may need custom configs.
Also, most websites need specific optimizations to make it perform better and a blanket config may help many websites but disabling customizations is more like saying there is only one config which you can use and limiting application specific optimization to a great extent.
It is definitely a support overhead.
It would be great for enhance to let use allow if we want to give access to config or not.
PHP is containerized and so it Redis.
We are able to customize PHP.ini or a per website level so why not Redis?
Note: Please don't take this personally. This is my opinion and I believe we should have a good discussion to help make enhance - enhanced!
