I've written routines for a GLCD. They are very controller dependent, ie no two are alike. The LCD command in the existing PICBasic is barely usefull to me, only if I'm "playing" with the X1 protoboard.

I used the Shiftout command, I set up variables per the LCD mfg instructions, and then used a freeware tool to "make" the fonts. These were all stored at the end of the program with Writecode, 3.5K worth. Most GLCD's (bare) don't have fonts. To encode that into PICBasic would be difficult and only possible on the chips with larger (8K) memory. Then people wouldn't like those fonts or that controller, etc. Not worth the engineering time in my opinion. Also, it is easier for YOU to do it than you think.

Also, many LCDs are now serial. So all that is built into the module, again the routines are different for each mfg. It would be like requesting a command for every I2C chip on the market, just too many.

And then you might find that the command is too bloated. I don't use HPWM anymore because it adds dozens of lines and computations to a simple process (once you learn it). Same for ADCIN, BUTTON, TOGGLE, and a few others. I don't mean that I use assembly. Set the CCPCON registers, done in 6 lines.