[Moto G5S Plus Questions & Answers] internetpilot:
To clarify a bit -- the phone is no more difficult to unlock, root, and ROM than the Nexus 6. However, the reason I gave it my "most difficult" award (haha) out of all the phones I've owned, is that gaining root on a device that isn't very well supported in the 3rd-party development arena doesn't really do you much good if you can't unroot just as easily. I can't get SuperSU working on this device, so I had to resort to Magisk (which is new to me -- I've always used SuperSU) and when I perform the unroot option via the Magisk Manager app, I end up with a "bad key" error on the bootloader screen and the ROM won't boot. The same thing happens if you try to restore all the original stock partitions via TWRP. Restoring any one of the boot, recovery, and one other partition that I can't remember results in the same "bad key" error. It's gotten to the point that even though I want to get it back to stock unrooted so I can grab the latest OTA security update (and eventually get the stock Oreo update when it's released), I really hate to mess with it. It's not because I think I'm going to brick it -- it's just I know I'll end up spending hours without a phone while trying to get passed that stupid "bad key" error, and then when I finally do that, my data partition will re-encrypt so I'll lose everything and have to set the phone up all over again. Since I'm trying to get it back to stock unrooted, I can't just easily restore my apps/data with Titanium Backup (because I don't have root), so everything is either gone or all messed up, so it's a huge pain in the posterior. Both versions of TWRP we have available for this phone don't reliably backup/restore the data partition either, so you can't rely on TWRP to backup everything if you want to mess around with flashing other ROMs, etc. That's what I mean by most difficult out of all the devices I've owned. When a new ROM is released, you really have to think twice before just backing everything up and flashing it to try it. You just might end up without a working phone for 3 or 4 hours before you get everything restored back to a working state.

I don't think you'll have a problem with Verizon. I know several people who are running 3rd-party Oreo ROMs on this phone on Verizon and they don't have the same issues I do with the carrier settings blowing everything up. It just seems to be Sprint. And to clarify my problems on Sprint, the stock rooted (and unrooted) ROM works flawlessly on Sprint. I can change the carrier settings, update my PRL, even use the "secret" dial codes to change APN settings, etc. But I can't do any of that on any of these 3rd-party Oreo ROMs. The carrier settings default to Global (which strangely works on Sprint's CDMA network), but I can't change Preferred Network Type to "LTE", can't turn on data roaming, can't change the CDMA roaming mode, and can't update the PRL or device config. Like Loccy said, all of the development on this phone is from India where the phone is very popular, so they probably don't know anything about Sprint. But even with these ROMs working fine on Verizon, how long will they be updated/supported? The Moto G6/G6 Plus is likely going to be released during the Summer, and that will probably fizzle the minimal development that the G5S/G5S Plus currently has. I think Moto is going to likely support this phone longer than the 3rd-party development community will.