We did multiple Tulip projects using a SQL database to avoid this issue. Works fine but it complicates development and we miss the analytics: this only works on internal Tulip data sources (tables, machines and completion records).
You can vote on this feature request to add analytics on connector data: Analytics on connector data
The workaround with workspaces or multiple instances is an enterprise feature, so not always available, and it is hard to manage compared to the app approval flow.
Any progress on the Tulip table lifecycle management would be much appreciated.