It looks like you can have a related table: Register a dataset as branch versioned—ArcGIS Pro | Documentation
- For datasets participating in relationship classes, the primary key of the relationship must not use the Object ID field. For more information, see Relationship class properties.
I am not sure about symbolizing on the related table from the branch versioned layers.
If you go back to traditional versioning, you would need to Reconcile and post edits to a branch version—ArcGIS Pro | Documentation, delete all the branch versions (not DEFAULT) then unregister as branch versioned then follow the traditional workflows.
I have NOT tested these workflows out: moving from branch --> traditional versioning, using REST API for related data
I would also recommend testing this in a DEV environment before making changes in a PROD system.
Thanks George Thompson for your quick response. I decided to stick with branch versioning, and using python to symbolize my data might be the only option I have right now. However, I think that's a little much for a basic GIS task.