I assume that you're not using collections to hold the data, and as such, not using them as the Items property of the Gallery. PowercrApps is horrible when it comes to i/o, so the less you do, the more performance. Well, there is no better performance, only less degradation.
The picture appears to show a detail form. How does the user get there? We have grid view, and the user picks the item to display in the screen. We write the item to a record variable, and that becomes the basis for the detail screen. If the user presses the Cancel button, then it's an easy throwaway. If they click save, then the patch uses the record variable for writing back to the actual SPO list.
All of our drop-downs are based on collections, to facilitate proper sorting.
If you want to get really radical, you can use a list that holds the datatype as one of the columns. Then, add code in the gallery to dynamically render the control with the data. (So, rather than having a detail screen, you have a gallery screen, and all of your list columns now become list rows, instead. (Transpose all the columns into rows.)
On an aesthetic note, change the display column names in the SPO List, such that you don't have ugly labels like "CMTLInk". Change it to "CMT Link" in the list, and that will self-propagate throughout the App. Notice that "CR Status" is non-conforming to every other label.
