In other words, we would need to seemingly move some workloads to Microsoft Flow (which is a great automation product otherwise) or Azure Automation. Unfortunately this adds a lot of complexity when building workflows, and SCOM->Orchestrator integration is good example.
It is a total scandal that Microsoft have ignored the Orchestrator 32bit part for years. With all the workarounds you have to do to make ORCH Powershell activities 64bit Powershell 5. It is a great mystery why they haven't fixed it.