OK .. but we are missing most relevant info.
Do you have any flatpaks?
Does arch-update never finish? If it does what does the output look like?
We can only guess its similar to the other threads because of the time and description .. and in those cases its flatpak/flathub causing the issue (or at least the way arch-update attempts to call it).
You might test this by applying various things like NoFlatpak or NoAUR to the arch-update.conf file and observing how it behaves in each case or together.