Time Machine works fine until it doesn't. And it won't tell you that a backup is broken until you try to restore from it. The errors are going to be cryptic. There is going to be no support and the forums are not going to help. The broken backup is not going to be able to be repaired. Time Machine uses the "fuck you user" approach of not providing any information about what it does, or doesn't, or intends to do or whatever.
If your data is worth backing up, don't use Time Machine.
I have been backing up to Time Machine for years without issues. Recently I started using pnpm (Nodejs package manager) and the backup process hangs on Mui material icons files (@mui/icons-material). Using "sudo fs_usage -f filesys backupd" I see that it is looping over the same files over and over.
There is a memory leak down the network stack (probably within security library/ TLS layer) that has been reported over 6 months ago but has yet to be fixed. Depending on the app's network usage this is leading to several GBs of leaked memory per day.
The best you can do is write the most concise example in an officially-supported language and file a Feedback.
It took about a year and a half or sofor both of my NSURL (one was pretty severe) leaks to be fixed, but this was years ago. Good luck.
And let's not talk about the landline broadband.... our rented appartment had a meager 1MBit download speed and 10MBit upload (yes, the reverse from what you would expect).
On the Autobahn, on many, many kilometers we had Edge only.
Compare that to my last travel to Iran: we had very fast LTE almost everywhere especially in the middle of the desert (it was heavily censored, but the infrastructure was working).
Even very close to big cities like Frankfurt, having an uninterrupted phone call is a difficult thing to have.