I haven't heard of any similar issues so far. I guess if I was in your situation and was on the verge of updating before noticing this issue, I would do it anyway and see if it improves the situation.

If it doesn't, then maybe check journalctl or logcat to fish for errors. But since I usually don't know where to look, I would certainly start by flashing the TWRP image to see if the touch screen works in TWRP. If it does, you've got an answer and it's a software issue. If I'm not mistaken, you should be able to flash back the SFOS hybris-boot.img boot image without touch input, so no dead end. Then back to journalctl/logcat to see what could be the software issue. At worst, you could backup SFOS in TWRP and flash a new fresh SFOS image, or even test Android, you'd still have your backup available if you want to go back.

Also, do you have SSH access to the device at the moment? This would be a good safety net if you could access the terminal from your computer without tinkering with the GUI.

If touch does not work in TWRP, you won't be able to do much in TWRP as far as I understand, unless there are command lines for all TWRP functions?

If it turns out to be an hardware issue (no touch input in TWRP), maybe head over the Discord server and ask someone in the #Pro1 channel: there are some people there who might know if there are some hardware connections to check inside the device. But in that case, best contact F(x)tec first to ask them for permission to try to open your phone yourself before sending it back for replacement.