I suggest to add a new function useRouteQueries to @vueuse/router add-on. The usage of useRouteQueries is similar but different to the existing useRouteQuery function in @vueuse/router.
For example, In useRouteQuery:

const page = useRouteQuery('page', 1, { transform: Number })
const pageSize = useRouteQuery('pageSize', 10, { transform: Number })
const name = useRouteQuery('name', '')
const ageGt = useRouteQuery('ageGt', 0, { transform: Number })
const users = ref<User[]>([])
axios.get<User[]>('/users', { params: {
  page: page.value,
  pageSize: pageSize.value,
  name: name.value,
  ageGt: ageGt.value,
} })

It will be more convenient if we use useRouteQueries that I suggested:

const  queries = useRouteQueries({
  page: 1,
  pageSize: 10,
  name: '',
  ageGt: 0,
  gender: null as boolean | null,
})
axios.get<User[]>('/users', { params: queries })

The relation between useRouteQuery and useRouteQueries is similar to the relation between ref and reactive.
The features in useRouteQueries is: It will only use the query params that the object passed to useRouteQueries defined. And it's type safe, it can infer the return value type of useRouteQueries via the object passed to useRouteQueries. And the values in the object passed to useRouteQueries is the default value. If the type of current route query param is different to the type that the object defined, the will use the default value, such as /users?ageGt=five will be ageGt=0 in useRouteQueries({ ageGt: 0 }).