Logo 3 may be a good choice, I will reconsider it.
quickbms is a name that everybody knows and it's there from almost 10 years so... no, definiterly no way I'm going to change it
quickbms supports more scripting languages than what you think eh eh eh
If you don't like the optimized mexscript language (based on the one made by mr.mouse decades ago) you can use C structs like:
for i = 0 < files
log name offset size
quickbms even supports most of the the winhex templates
If you have an additional documented language and it makes sense to add it, I can support for it in the next versions of the tool.
First I need to know what you don't like of the current language, it's so basic and simple that I can't believe you have problems with it