Agree that 'technical debt' could encompass conceptual debt in its broader definition. But, at the companies I've worked in people often don't use the terminology technical debt to include conceptual design issues. Technical debt discussions often focus on the programming language/database issues. I've found it useful to have a shorthand for referring to unintuitive products and codebases that stem from poor product design choices rather than poor language/tool choices.