Current solution involves manual creation of an XCOde project which interally calls Python main.py using CPython code: https://git.qt.io/ece.cinucen/pyside-test-gui/-/tree/main/pyside-test-gui?ref_type=heads

We would ideally love to use kivy-ios (https://github.com/kivy/kivy-ios) because we already use python-for-android for Android deployment and the workflow is the same. As such the workflow would be:

1. Create local recipes for shiboken and PySide which would unpack the cross compiled iOS wheels as can also be seen for the Android recipes. See sources/pyside-tools/deploy_lib/android/recipes.
2. Additionally, make any changes to the template in kivy-ios depending on the requirements for supporting PySide and Shiboken - https://github.com/kivy/kivy-ios/tree/cce95455ec1f4c6d0eadc0ff168d58db676bc96b/kivy_ios/tools/templates Since you would call qt_main_wrapper from libpyside, you might not need much changes here. 
3. Create a tool `pyside-ios-deploy`, just like `pyside6-android-deploy` that would call kivy-ios and deploy the project.

Changes in python-for-android to support Android: https://github.com/kivy/python-for-android/issues?q=is%3Apr%20author%3Ashyamnathp