it’s tricky because, for example, some NES games have garbage on the extreme horizontal (SMB3 has a border on the left, and scrolling artefacts on the right), and some have useful parts (Castlevania’s UI extends the full width), so you might want to crop for some, and not for others, and you might only want to crop the horizontal overscan, and not the vertical, or vice versa.
arcade emulation rarely seems to have overscan you’d want to crop because (theory) they didn’t have to worry about consumer TVs with various viewable amounts of overscan, because the CRT of each cabinet was adjusted by the engineer. with arcade stuff you mostly have scores and useful stuff right up to the edge.
personally, i think having a global ‘crop overscan’ option isn’t going to be much use across many cores, and it’s better to have it as core options (if at all) where the emulator authors can pick appropriate defaults, and appropriate levels of control. eg, with NES you’d want to control vertical and horizontal overscan separately, and with arcade you’d not want to have any overscan options.