you can do semi adaptive with CC and a post processing step
(https://fenrus75.github.io/FenrusCNCtools/javascript/gcode2gcode.html )
that javascript program will track tool engagement for each segment of the gcode, and scale the feedrate as if the tool was 50% engaged. It’ll go slower on slotting (and those corners where CC moves from one “ring” to the next “ring”), and it can go faster (upto the speedlimit you set) for when the engagement is less than 50%.
right now you likely set your feedrate to the worst case of the whole toolpath… .this kind of processing changes that so there is no worst case (the worst case is usually 2x the normal case)…