Thanks for your bug report. This is the intended behaviour. In cases where a network uses the same prefixes for PREFIX and CHANTYPES, there will always be an issue determining whether a word begins with a nick prefix or a channel prefix. This issue was indeed discussed the last time the hotlink feature was tweaked to make it work in as consistent a way as possible given that it is parsing plain, non-delimited text with conflicting prefixes.
