I assert that this was the original intent of the usage. If you look at the man page in the archive here: https://groups.google.com/forum/message/raw?msg=net.sources/...
you'll see "screen is a full-screen window manager that multiplexes a physical terminal between several processes", describing a piece of software that - at that point - didn't do any splitting or tiling.
multiplexer or multiplexor (ˈmʌltɪˌplɛksə)
noun
(computing) a device that enables the simultaneous transmission of several messages or signals over one communications channel
A USB hub multiplexes a USB port by making it so that multiple USB devices can be connected to the same port and all pretend that they're the only ones connected to it.
The Ogg container format multiplexes a bitstream so that multiple timecoded media streams can be streamed through the same data channel and pretend that they're the only things going through it.
An preemptive-multitasking OS kernel multiplexes the CPU so that multiple processes can run on the cpu and all pretend that they're the only ones on it
A terminal multiplexer multiplexes the terminal so that multiple processes can output to the terminal and all pretend that they're the only ones using it.
That describes the window management functions of tmux.
It does apply with 100% to what it's meant to be applied: multiplexing terminal IO.
It has nothing to do with "window management". In fact it could also offer no window management at all, except for switching between sessions, which is was what it did initially.
Multiplexing is a well known, precise term, and terminal multiplexing as a technique existed before both tmux and its introduction of tiling (e.g. screen).