It all depends on your use case. I can see some deployment situations where the ops people would be the ones asking for tamper resistance. If you're running a small shop with only few people and you're not in banking or some other branch of industry where mistakes are very costly then separation of concerns is probably not your main worry.

But if you're operating with some auditor looking over your back then it can become a very powerful argument for using some technology over another.

As with any tool: use it where it is appropriate.

This all assumes that docker will make tamper-proof an option, not mandatory.