In addition to Bob's comments, a little background may prove useful ...
As far as Time Machine (TM) backups to a Time Capsule (TC), there are basically three things in play:
- The format of the Mac's internal drive that will be the source for the TM backups. Prior to macOS Big Sur, the format was HFS+. For Big Sur to Tahoe (currently the very latest), it is APFS.
- The format of the TC's internal drive. This drive is always formatted in HFS+ which is required by TM.
- The network file sharing protocol being used. AFP = Apple File Protocol, and SMB are the most commonly used. Apple will be phasing out AFP; most likely, in the next release of macOS.
When a Mac running Big Sur or later makes a TM backup to a TC, it still creates an HFS+ sparsebundle disk image on the TC. Inside that sparsebundle, the backup volume itself is HFS+, not APFS — even though the source Mac’s internal drive is APFS. The Mac performs the translation automatically, meaning your APFS-based system is backed up to an HFS+ Time Machine volume. However, because of this, you don’t get the efficiency and speed benefits of the new APFS-based TM format introduced with Big Sur (which requires a directly attached APFS drive as opposed to the networked TC).
So, the TC still works, but it’s treated as a “legacy” network destination. The main trade-off is slower incremental backups and less efficient space usage. If you’re running macOS Big Sur or newer, Apple’s TM prefers SMB over AFP, but the Time Capsule’s older firmware doesn’t handle SMB-based Time Machine backups properly, which is why AFP remains necessary in that setup.
Going forward, hopefully you can see that this is not a simple matter of just "re-imaging" the TC's drive. It would require, most likely, a new system board on the TC as well ... and, since Apple has gotten out of the network hardware business back in 2018, there's little chance that they would get back in with an updated TC.