Remove default filter values for `start` and `end` on timeslot endpoint?

From a frontend perspective I don’t really see any value in defining default values for the start and end fields applied by the backend. If anything, they make it harder to achieve certain things. Currently, the default start value is the current date at 00:00 local time and the end is the start date + 60 days at 23:59 local time.

In my specific use-case I want to query all timeslots that start before a certain start date. This would be a new filter because start filters with gte (greater-than-equal) – though not the topic. If I set this filter (let’s call it startBefore) I don’t want any start and end values, because they would change the behaviour of my query.

I kept the default values when I refactored the filter many months ago, but never questioned their reasoning. Is there a reason for them? I don’t see a any practical upside, but only downsides.