Any terminal that has rich pane manipulation semantics can serve to take the place of tmux, this includes kitty.
The one thing kitty can't do, however, is have a remote session that keeps your workspace intact. I, and many other devs, purposely disconnect our development from any given machine we're on.
The majority of reboots or other disruptive behavior is because of desktop machines (for those of us that don't use Linux as our primary and only desktop OS); running the tmux session off another machine (even if its just a headless machine under our desk) minimizes disruption due to GPU/etc bullshit.
I want to add that I've been using tmux for the last decade.
I went from gnome-terminal, konsole, multiple remote ssh sessions (tmux on the remote side for long running sporadic jobs like repairing databases), Windows Terminal, iterm, iterm2, kitty, putty, etc etc etc. From ancient Ubuntu (from CD-ROM giveaway era), to modern MacOS releases, from several Windows releases.
Happy camper of wezterm for the last 6 months. Alacritty as secondary, Windows Terminal on my gaming machine (wsl2 for some stuff).
Between them: still the same tmux config, just evolving, changing plugins, colors of the status pane, adding starship.rs to the mix. Very tempted to try zellij harder, but not sticking to any of these terminal interfaces provided me lots of flexibility and consistency.
even locally, when the GUI hangs and i need to restart it (Xwayland still has issues), having most of my work in local tmux sessions saves a lot of time after logging back in.
I had this for a while, I suspect a lot if users are like me (and I assume you) in that the functionality they need from tmux is more or less just tabs and splits (tmux does more than this, but I don't tend to use those features) which kitty replaces pretty nicely.
Since I work across actual Linux and WSL I really appreciate having something that's terminal agnostic like tmux since it means I don't have to have a separate set up when kitty isn't available.
Discovering tiling window managers (it was i3, I now use sway) stopped me using it - I only really did for tiling I suppose, then discovered I could have that for other apps too.
The one thing kitty can't do, however, is have a remote session that keeps your workspace intact. I, and many other devs, purposely disconnect our development from any given machine we're on.
The majority of reboots or other disruptive behavior is because of desktop machines (for those of us that don't use Linux as our primary and only desktop OS); running the tmux session off another machine (even if its just a headless machine under our desk) minimizes disruption due to GPU/etc bullshit.