There’s nothing wrong with using a google sheet as the data source for choice components, but I think what @Uzo is saying is that if you can migrate any data into glide tables, then it can help reduce the amount of data that has to syncronize between glide and google. If it’s static data, then no it’s not going to make much of a difference, but any sheets that have data updated as well as being located in a google sheet will count against sheet edits.
There’s no functional difference between glide tables and google sheets as far as the app is concerned. The app only communicates with the data stored on glide servers. It’s the glide servers that then synchronize data with the google sheet. If there is functionality that can only be achieved in a google sheet, then you will have to rely on using them. If functionality can be achieved by only using glide tables, then it’s better in the long run because you will not have hits to your sheet edit count and it’s less overhead and cost for glide to keep that data in sync. The only real downside to google sheets is that any calculations that happen on the google sheet side will take a few seconds to minutes to synchronize back to glide. Doing those calculations on the glide side is instantaneous with no delay. Just synchronizing basic column data from glide to google will have no affect on the app, but when things change on the sheet side, then you can see delays as it has to synchronize back to the glide servers and then back out to the user’s app.
Some of my apps are older and were created prior to glide tables existing. Some functionality is only achievable within google sheets, so I still heavily rely on google sheets, but I’ve been trying to do more and more exclusively in glide tables.
It basically comes down to if you think you would ever need some functionality that is exclusive to google sheets, now or any time in the future. If you don’t think you ever will, then I’d say go for using glide tables exclusively. It’s nothing to overthink about. Google sheets is like a backup of the data stored in glide, but the difference is that they both synchronize both ways. If data is sourced from a google sheet, then any change to any data in a row at that exact moment will trigger a sheet edit as it synchronizes to the google sheet. If you are using entry components on a detail screen as opposed to a edit screen, then each and every change on that screen could potentially trigger a sheet edit since it’s updating the data in real time. Using an edit screen only updates the data once the user clicks on submit.