That's some valid criticism, let me address it.
A BIP-39 phrase is an encoding of a binary value. If you want to "compress" the phrase, you can use the binary value instead. It can't be compressed any more than that.
We are talking about compress to human-usable format, not binary formats. The computed seed for that textual representation is
eac38d38b91495d46f12e28790c78cf7c5da2937f3b1ff7332ad68007f06316e8156be8520dc880db3946fac8e0e896f6ce27a367e204ac3feb50676a56ab10c
...or decimal 7377687107399363427919506940445526085943085060767798863389917008452289517492375
9375047662272726680500679881548796212384941982210304075203137347288298516924490
7766500354732069958083853735531831032887267586702456712895290533588458780
This has no use for humans, it's the computer technical part.
If you want text, I think base-64 is a better choice, because it is more compact and more widely used.
Even base58 is too much, base46 would be the ideal base size [sqrt(2048)]. Base64 wouldn't give any advantage, the whole idea is to compact a number in maximum of 2 chars.
The bigger danger is making a clever backup that only one Python script understands.
You can even do it by hand with pen and paper, sorry for use GTK in the sample Pyhton, all you need is to split it by pairs, convert it from b58 to decimal and check what line number it corresponds to in BIP-39 wordlist, even Windows Notepad can show line numbers, and if you open in Github instead of downloading the file, Github UI already shows you to the line number.
Using: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt
5d = decimal 268; line 268 cannon
EF = 768 = garment
Bh = 620 = estate
BF = 594 = enforce
(...)
As for the "+" it's to remind you that is not the whole seed, the whole purpose of add a custom word to the derivation path is so that if someone gets your seed backup won't be able to get your funds, but you can write it like:
5dEFBhBFS6345XuAdSQZeT2LMQP6d+<your custom word>