To amend my second question, I did not realize that "navigation controller" referred to an old peripheral that I neither have nor care about. So long as the caveat about the buttons doesn't also apply to the regular move controller, I don't think it should be much of an issue.
I gave the pairing workflow a try on Windows 10 Pro. I was able to pair one PS4 move controller successfully, but pairing the other one via the same method fails:
Here is the command output for pairing the second controller:
"""
C:\Users\aeva\Downloads\psmoveapi-4.0.12-windows-msvc2017-x64\bin>psmove.exe pair
Connected controllers: 2
PSMove #1 connected via USB.
Unplug the controller.
Now press the controller's PS button. The red status LED
will start blinking. Whenever it goes off, press the
PS button again. Repeat this until the status LED finally
remains lit. Press Ctrl+C to cancel anytime.
Connection verified.
Pairing of #1 succeeded!
Controller address: (redacted 1)
Calibration data available and saved.
Error connecting to PSMove #2"""
Event viewer had some generic errors logged from my attempts: "Initial connection to Bluetooth HID device failed. The device has been removed as a personal or paired device. You must reinstall the device."
HOWEVER - it looks like I was able to pair both devices by turning off the successfully paired one first, then pairing the second one. From there I was able to turn both on and successfully
run psmove.exe list with both connected as bluetooth:
"""
Host address: (redacted 1)
Controller 0: ←[
(redacted 2)
←[0m (Bluetooth, battery: 100%)
Controller 1: ←[
(redacted 3)
←[0m (Bluetooth, battery: 80%)
"""
Huzzah! I don't know that I wont run into other problems trying to use both controllers over bluetooth at the same time, but it seems like I can at least pair them both and have the lights change colors.
So, I think that mostly just leaves my questions about compatibility with the buttons and cameras?