You know, the situation is, in fact, rather parallel to ideogrammic versus alphabetic written languages.
Having particular signals for half pressure, kpsi, safety stop, etc. is similar to the way Kanji functions. You end up having to memorize a larger set of signals, but anything within that vocabulary can be signaled directly without "spelling it out".
On the other hand, using one handed numbers for digits and signals for generic things (such as one signal "level" for the depth to swim along a wall, the depth of your deep or safety stops, etc.) means you have a much smaller vocabulary, but instead of saying "safety stop" as a single signal, you end up saying something like "ascend-level-1-5". It would be similar to how our alphabet works.
With the "alphabetic" signaling methods, you trade longer sentences for flexibility and simplicity. If you want to say, "let's do a 5-minute safety stop", you just signal "ascend-level-1-5-hold-5-minutes", for example, which would be exactly the same sentence as a deep stop, just with different digits (e.g. "ascend-level-7-5-hold-2-minutes").
I taught the basic signals to my buddy's dad on the ride to a dive. All he needed was "pressure", "depth", "NDL", "time", and the digits, and he was able to communicate all the pertinent dive information we like to share. He had no idea what deep stops were, and he wasn't that interested in air consumption (other than our rock-bottom plan), but we incorporated all that without any difficulty. That pretty much sold me on the "alphabetic" manner of primary dive information communication. For things like flora and fauna, sure, we have a signal for each, but for "buddy/plan management information", we're solidly in the "simple words in sentences" camp.