Are there that many people with iPad Pros who do not have the folio or Magic keyboard?
Also, I feel like the solution is to release an "App" that has a virtualization server in it, that can run MacOS. Keeps it contained, off to the side for the devs, but can take over the screen and inputs and be a fully-fledged touch MacBook to those who want it. (Maybe require dev accounts?)
Perhaps we should consider that the text-based approach to programming is inadequate. That maybe a process that requires large physical monitors and large physical keyboards should adapt to an era where a lot of computing is done on small mobile devices.
Mouse support is still hidden under several layers of menus despite iPad OS advertising it as a feature.
For Xcode they could take a page out of Android's book and enable it under a "Developer Mode".
Development needs a proper keyboard, and a significant screen real estate. An on-screen keyboard shared with Xcode's UI, and further splitting the screen with the app being developed would be very cramped.
iPadOS also has no consideration for command-line tools and shared things that don't belong to any app-silo. If you ever needed something not built-in into Xcode.app, it'd be awkward clash with sandboxing. Is Xcode build supposed to launch a Siri Shortcut of Ruby.app to run a script, with all the GUI animations in between?