Hello to all,
I had no lasting major issues installing or running 14.3.x betas, and 14.3 final, on MacBook Pro 5,2 (2009) and iMac 13,2 (2012). On few occasions a full installer was needed to install some of the betas, but mostly upgrades were accomplished via OTA (and nightly OCLPs). There were issues with blue tooth connectivity and, predictably, MacBook Pro 5,2 (non-metal) could not run certain "Metal-dependent" applications.
However, beta1 14.4 is another matter. Much as already reported by other posters, Sonoma 14.4 beta1 does not fully install over 14.3 final, and results in "prohibitory" sign when attempt is made to upgrade via either OTA or full installer mode. That is true for both iMac 13,2 and MacBook Pro 5,2.
Interestingly enough MacBook Pro 5,2 appeared to complete the installation OTA, using OCLP from 1.30.24, and actually booted into the log-in window. In previous reiterations of Sonoma, when stuck at login, attaching wired keyboard and mouse to a modern USB hub, then plugging the hub itself to USB port of the MacBook Pro (credit hvds) did allow connection, and hence, ability to type-in password, and proceed to fully functional desktop. Experimentally, I pressed space-bar while booted from USB thumb drive, and Sonoma 14.4 beta1 recovery volume became available; selecting it allowed boot to proceeded without prohibitory sign, but did stall with flashing icons for mouse and keyboard on the screen. Plugging external mouse and keyboard via USB hub, as described above, did not change the outcome. Neither wired keyboard nor mouse were recognized. This is in contrast to Sonoma 14.3 series, where external mouse and keyboard solved the problem. A USB bluetooth dongle plugged into MacBook Pro's USB ports showed that none were energized (its blue led was not activated).
There is enough of a trend to suspect possible problem with USB ports; this was already mentioned by K two, and referenced to possible related issues in threads discussing supported Macs.
iMac 13,2 fared no better; choosing 14.4 beta1 recovery volume allowed installation to proceed, but process stalled on second reboot, with progress bar barely initiated; there was a kernel panic message on subsequent reboot.
Great work by developers, who have an "eternally" moving target with updates.
Hope this post may be of help.