I think it might be good to understand how all of this works (integrating all these software solutions). This is how I do it every night. My mount is mounted permanently on a pier in my backyard, so I rarely need to polar align it. When I do, I use SharpCap Pro, which costs about $10 per year. NINA can now polar align and it is free.
I have a case with a mini PC and a power distribution box I built. The power cables for the mount, imaging camera stay at the scope. USB cables for all the stuff stays at the scope (mount, imaging camera, guide camera, auto focuser). A powered USB hub also stays at the scope.
I carry the case to the scope, which is covered with a TeleGizoms cover.
Uncover the scope.
Plug three power cables from the scope set-up into my power distribution box. Plug one USB cable from the hub into the mini PC. Plug the power distribution box into a 48 AH battery. Once I connect the battery to the power box, the mini PIC starts by itself.
Remove the caps from the guide scope and the main scope.
Go inside the house and turn on my MacBook Pro. There is a dedicated router just for my imaging system in the case.
Connect the laptop to the telescope's network.
Open Microsoft Remote desktop on the Mac.
Start the Celestron CPWI software for the mount. I have a Celestron mount and this is the software that controls it.
Start PHD2 the auto guiding program and connect it to the guide camera and the Celestron CPWI software for the mount.
Connect NINA to CPWI, PHD2, the Imagining camera and the ZWO Electronic Auto Focuser. This is where ASCOM come into play, it allows are these programs to communicate with each other.
All these software connection are a single mouse click. I takes about 5 minutes from the time I carry out the computer case and battery until all the software is connected.
I could reuse imaging sessions from past nights that are saved in NINA, but in this case (for an example), I will open Stellarium, which is also on the mini PC. Note: all the software is one the mini PC. I am just controlling everything from the Mac.
So let's say I want to image the Orion Nebula (M42) for 6 hours. In Stellarium I do a search for it and it comes up on the screen.
Now I go into NINA and tell her to get the coordinates from Stellarium, by pushing one button in NINA.
Now I go to the "Sequencer" in NINA and tell her I want to take 360 60-second exposures. There are some other settings, which are already set up in a template, and I want to keep this simple.
Now I hit START.
NINA tells the mount (via CPWI) to slew where it thinks M42 is. NINA takes a picture, and sends it to the ASTAP program for plate solving. This is already set up in NINA for every use.
ASTAP plate solves and sends the information to NINA. If M42 is not centered, NINA sends another command to the CPWI software to move the mount. Then NINA takes another image. Usually the second image centers the target perfectly.
Now NINA tells PHD2 to start auto guiding.
Next NINA starts taking test images to adjust the auto focus. After each image NINA makes a focus adjustment and takes another image. Once NINA confirms the focus is optimal (2-3 minutes), NINA starts taking pictures. I monitor the first few just to make sure everything is working as it should, which happens 99% of the time.
Now it is 7 PM and I spend the evening with my wife. I can ignore the telescope.
If, during the night, M42 crosses the meridian, NINA will stop everything, tell the mount to switch positions, and then plate solve, restart guiding, auto focus, and continue to take the remaining images.
After 360 images are taken, NINA parks the mount (so it stops tracking) and turns off the cooler in the camera.
Around 8am or 9am (I'm retired), I copy the images from the mini PC to a USB drive. Shut down the mini computer with the Mac, put the lens caps back on the scopes, disconnect the cables, cover the scope, and carry my case and battery into the garage. I plug the battery in the charger. Done. Another 5 minute task. It takes longer to make a pot of coffee than the morning astro tasks.
I am not advocating that my software is the best way to go, but it works perfectly for me and I don't see any need to change. You have a great mount. If I had your mount, I would use the same stuff only substitute CPWI for whatever software controls your mount.
The point I am trying to make, is you need to figure out what all the pieces (software) do, and how they integrate (work). From what I have read, the ASIAIR does all of this, but users are stuck with the ZWO universe (e.g., ZWO cameras, ZWO auto focusers, ZWO filter wheels, etc.). Plus the software isn't as robust as what I use. Plus, I don't think you can control it with a computer (I may be wrong). I have a Celestron auto focuser on one of my scopes, and it is incompatible with the ASIAIR.
I do all processing on my Mac. I would get all the acquisition stuff down before buying processing software if I were you. Some people struggle with all of this at first. Others, like me, had very few problems getting it all to work, other than self-induced issues such as not reading all the instructions.
I have used Photo Shop (CS2), Affinity Photo, Astro Pixel Processor, Star Tools, and switched to PixInsight a couple months ago. I sticking with PI, However, all the other software packages I used over the course of a year, made PI much, much easier to learn. Although, perhaps, one never learns everything about PI.