Forget about terminfo, example 274727:
Here's an article about diffences in terminals: https://utcc.utoronto.ca/~cks/space/blog/unix/TerminfoAndAutomaticMargins
It tells you that you could check terminfo for the "bw" capability (or "auto_left_margin" in readable).
Only if you do that, you'll find that the only vaguely in-use entries that differ from xterm-256color are Eterm-256color, foot and rxvt-unicode-256color.
Of those three, I consider only foot to be worth supporting (rxvt is dead and eterm is pretty bad and there are better alternatives even in emacs).
And the article already tells you that screen behaves unlike its default terminfo entry and xterm does it wrong. So if you need to know the capability you already need to add quirks for those two.
So the difference is between adding quirks for three terminals or adding quirks for two and linking against a whole-ass library and depending on files on the system.
And then you have terminals that use a terminfo entry by default but behave differently - a cursory glance tells me it's putty and some versions of screen.
And it is always like this. For every capability there is a case where terminfo is wrong and so you need to add quirks anyway, so just ignore it. Even where it would get you a bit more right (and there are cases where it makes you more wrong), linking the library and reading the file simply are not worth it.