I have already found it before: the Basic pointers are beginning at $65 (101), where the first pair is the start of Basic memory, whereas the second is the end of program pointer (the first free byte after the program code as usual, and probably the variable area is starting afterwards), so it is at $67-$68 (103-104), you can check it easily.
Yes, but ... If you check the source of the emulator, I've already done that exactly
Since you mentioned my method is not perfect, so my assumption, that there are more pointers should be set, than just these (well, the beginning should not be bothered too much anyway).
Anyway, a quick comparison now on layout of these pointers for C64, C128 and Plus4 revealed, that the addresses can be different, but it seems, the order is the same on all of these machines with the very same meaning. Thus my conclusion that what $2B/$2C on the C64, should be $65/$66 on CLCD basic, and just by guessing, the 7 pointers from there are the same on C64/128/+4, so my idea that probably it's true for the CLCD too: after all if Commodore has managed to keep the same order of these pointers at a single place (even if the actual address varies), I would guess it's true for the CLCD as well. By assuming this is true, I guess there is well known solution for C64 how to do this, so then just the solution should be offset'ed to the CLCD zero page area for the very same meaning.
Btw, meanwhile I've put a memory dumping menu item, and basic load/save items as well. I need the implement the "right policy" though.
It was just a quick 15 min check/compare (of memory maps of c64,c128,plus4) and hack (in Xemu), so of course it's not ready or in the official Xemu repo yet. Maybe tomorrow if I have time, it seems it's not a big deal to do, I mean shouldn't take too long for me.