I think the people above have presented the pros and cons of the remote approach and you have pretty much defined what’s non-negotiable in your latest post. You have an iPad, give your proposed setup some testing - you probably don’t have the Citrix Mouse, but some testing will give you a good idea of what the limitations are (besides which, support for a mouse in iOS is rumoured, so I would hold out on an expensive Citrix mouse).
As can be seen above, I’ve been unable to go 100% iPad. When I hit the iOS app version limitations in Office for example, I save the document on Dropbox or iCloud and complete the job on my MBP (2018, keyboard still fine ). I could leave a Mini running permanently so I could remote in, but it seems just so inefficient. I rather just batch my work. A good example is what I did last night: I downloaded a .dotx file from our Confluence server to my 12.9 and proceeded to carry out edits on it, required for the new version. One can’t (at least I don’t know how to) access custom doc properties to update a field and I’m not 100% if I can save as .dotx once more. So I saved it on in a dedicated “share” folder I have on Dropbox and I’ll complete the edit when next on my MBP. It’ll take another couple of minutes once there and I’ll update Confluence once more...nice, clean and efficient.
I’ll go into a little more detail. I’ve got an original 12.9" Pro with SKB, that hangs around the house and is the general workhorse for, let’s call it, general work, I.e. anything that doesn’t require a desktop version. This includes remote support with MS RDP and Teamviewer. When at the office or traveling, I carry the MBP and my new Air 3 with SKB (and Pencil, that I share between the two iPads). I’ll often spend half the day at work on the Air 3 before moving to the MBP to do some work that requires a Windows VM, including some development, or some touch-ups on Office docs. When on the road, more often than not I work solely on the Air 3, with the occasional need for the MBP where I need Windows resources (we develop micro-based products using tools that only support Windows).
So overall, a hybrid lifestyle is great, and quite efficient from my perspective. Plus, I get to work on and enjoy both platforms. Try some things out and play around a little, your workflow will come to you.