Probably this could be a basic workaround for your need. 

But this can be achievable by customization.

By setting a UI-Model as a “Master Control” and a UI-Field to handle a Render Condition on those fields you need to show/hide.

Plus, consider a Button set to turn on/off the render condition.

refer to this XML page sample:

https://gist.github.com/feramirez505/20b352c3aae74172111b4ac7c0ed7266

Hey Chad, you know, I don’t think that we’ve actually talked about this one. It’s a great idea though. It seems like a natural extension to the behavior of the table.

We loosely call features like this our “personalization framework”. We have talked about a number of improvements that revolve around giving the end user more control over their experience. I’ll add this one to that list for future consideration.