So yes, unfortunately, for a Custom View Tile (or most tiles) to be valid, they need to be configured. This is what triggers the Jive instance to notify the backend that the Tile has been installed, and allows Jive to execute the rendering phase.
This is feedback we've heard before and I've made another note of it for engineering consideration, but we will have to see where this falls in the prioritization exercises.
In general, the proposed solution would be a way to indicate in the tile > definition.json, such as "configurationRequired" : false, in order allow the registration to happen automatically.
Hope that helps to at least help you understand what is going on.