When tomatoes, olives, capsicum and zucchini are ‘fruit’ then the definition isn’t serving it’s purpose for anyone discussing cooking or eating or procuring those things. It’s a different meaning of the word that’s useful in particularly narrow settings but useless outside of those settings. The only reason people like to repeat the claims of ‘technically a fruit’ for various vegetables, outside of the context of maybe agriculture or scientific research or horticulture is because it’s amusingly counterintuitive and contrarian which is exactly why it should be disregarded.
I guess if, as this person says, the intended use is made clear then presumably so long as the original logs from which the report was generated are retained then there shouldn’t really be an issue. Make your nice, digestible reports that normalise over a workday and give a more grand overview of progress, and if they smell a bit too rosy or you just sometimes need a more granular accounting of time then clients/bosses can request the original raw data from the contractor/employee. Maybe this software itself should include some ability to retain a log of the processing that was done so that the relationship between its generated reports and the source data can be more clearly audited if some kind of a trust issue arises.
The hope I guess would be that you make it clear that this is a more executive summary style of report that you’ve added as a courtesy because it’s more useful in context and that’s hopefully enough for whoever you’re reporting to but if they want more transparency or detail it’s all there for them too.