As for load-only orders, after some looking at the code and thinking, I suspect that some potentially not insignificant rehashes may be needed to get them to work well with cargodest.
The problem is that on arrival at a station, the single hop route creation/update routine builds a route from the last station to the current station. In the case of load-only orders, there are suddenly multiple "last stations", of which only the last is saved.
In your scenario, how does cargo get to point B, if neither of the routes unload cargo there?
I designed cargodest so that regional and express type scenarios divided cargo automatically. As routing is based on estimated time to target through the next hop (ie. fuzzy metric based packet switched networking). It's possible to make cargo be routed more strictly by adjusting some of the config parameters. (In particular setting cdstrtdiffmax to 0 or cdstrtcmpfactor to 65536 will only permit cargo to use the single quickest route to the destination (which usually means not unnecessarily using local lines, unless your express lines are overloaded or relatively slow)). However, the defaults should also do the same in most cases (and work much better than the above when networks have mesh aspects).
Using lots of load-only orders brings the question of how cargo gets to those stations (unless you're using them as pick up points only).
I've not been able to reproduce the dialog box text title issue at all. So I'm not sure what the issue is.
Try renaming ttdpttxt.dat, re-running mkpttxt.exe and/or fiddling with some of the GUI/game options and see if the problem goes away.
As for the station clicking crash, I've reproduced that and will aim to fix it ASAP.
However, today I really ought to be to be doing my uni worksheets on PDEs and fracture mechanics instead

, and on the weekend, I'll be busy and not using a computer as I've got some... business to take care of

.