I also struggled with many components inside QTable. I replaced them using native html with quasar css:
<button tabindex=“0” type=“button” class=“q-btn inline relative-position q-btn-item non-selectable q-btn-rectangle q-focusable q-hoverable bg-white text-black”><div class=“q-focus-helper”></div><div class=“q-btn-inner row col items-center justify-center”><div>Standard</div></div></button>
This is not good long term solution but I agree that we need some functional components built in into framework - for exapmle: QBtnSimple, QIconSimple etc… This way we can avoid that future change inside framework css will break my native button styled using quasar css. I will create feature request for that using Github. Not everyone knows at the beginning why some components work so slowly using sub components.