Patrick,
The file "sources.download" is a special file needed for the Koji build system (it is the instruction to Koji where to download large sources). Your modification is not needed unless you are planning to use a similar build system (which I guess you do not have). Also, your suggested update is not complete, you need to generate a new SHA256 checksum (the "8282cb71c924b6ef92503976d50f966f2c785eab8f8cffa1136ac133f0241157" is for the old domoticz 2022.1 source).

You need to download the source and then calculate the checksum by doing something like this:
Then you copy the output and replace the old checksum in the sources.download. But as I said, when you build manually the file sources.download is not needed at all.

Everything else is OK. The "old" patches should be there unless Domoticz upstream have changed those parts. Without the patches it will not work as intended. In fact, If the old patches work, you were "lucky" this time. There will come a time when the upstream code have changed so much so that the patches will need to be modified. In fact, the Domoticz upstream is not intended to run on such old Linux version as ClearOS 7 so it is just a matter of time until it can't be fixed unless you run Domoticz in a virtualized environment on top of ClearOS if you still like to stick to it.

In addition, if you are running Z-wave: The upstream open-zwave is sort of dead, and even if it was not I do not think it is possible to compile newer version of it anylonger on ClearOS after they introduced the Supervision class last year. I have at least not been able to do it. That means that you will not find any support for new HW models that may enter the market. Domoticz and other home automation softwares have switched to ZwaveJS which have MUCH better support for the Z-wave protocol and is actively supported/developed. Unfortunately (if you ask me) it is not based on a "proper" programming language as C or C++ that can be compiled into a executable suitable for a rpm-package, but is based on Javascript/TypeScript which requires a NodeJS platform etc which in practice makes it a no go in a ClearOS environment (I tested it locally on clearOS and got it to work, but this is not the same thing as an uppgradable system ready for 24/7).

Finally, my recommendation for an alternative "all-in-one" home server would be TrueNAS. At least if you can keep it within your LAN and do not need firewall etc. One of the real advantages is the ZFS file system and the monitoring that goes with it. They have 2 versions "TrueNAS core" and "TrueNAS scale". The core version is based on FreeBSD and is old and very stable. The "scale" version is based on Linux and is almost "too new". The TrueNAS scale is what I personally would use, but I could not: TrueNAS is a "closed environment" which means that you need to install any apps as docker containers which has many advantages, but also some disadvantages. My motherboard do not support "VT-D" hardware virtualization pass through(Both CPU and motherboard need to support it) which means that I cannot assign physical HW directly to my docker containers. With Z-wave USB-dongles etc this was a stopper for me.

An alternative can be openmediavault as it is based on the normal Debian distribution which allows you to install applications such as Domoticz and openzwave directly on the host system. The operating system is also so modern that you can use the Domoticz installation files without the need for patches etc. Openmediavault also has the possibility to use ZFS through the omv-extras packages. However, any packages you install yourself on the host will not be maintained by the automated scripts etc, so this puts more responsibilities on the owner of the server...

/Fred