I don't know what wml2wmlc actually does, but WAP devices don't read "compressed" data but "compiled" data. The gateway handles this (get WML page from normal server, compiles it into some kind of bytecode, passes the bytecode to WAP device).

Knowing the compiled size of your WML pages is a great advance, since devices like WAP phones have limited RAM (a Nokia 7110 gives up on compiled pages over 1400 bytes!).