Store custom sorting information (multiple fields sorted) in an item's properties in the geodatabase. When the item gets added to the map and the attribute table is opened, the attribute table would get automatically sorted via the saved setting.
Use case described here: Sort rows in existing feature class
A sorted database view wouldn't help because the data needs to be editable.
I'm aware that maps/projects, .LYRX files, etc. can store sorting information. But we don't use those mechanisms in this case; we add the item from Catalog into various maps, as needed, since the table is only used occasionally.
