LodgingReservation / LodgingSearch extension

I'm looking for some design advice: I work in the hotel industry and our
platform currently uses a number of key elements from the Hotel ontology
(Organisation, Brand, Hotel, HotelRoom, Offer, LodgingReservation
<https://schema.org/LodgingReservation>).

These preexisting elements have allowed our tools to automatically
recognise our clients hotels sales funnels. We can identify what hotel we
are on, what rooms the hotel has available for a given search and when the
user makes a purchase. One area that we would like to support is
identifying the search parameters a user entered for making a reservation.

The data we would like to capture is virtually identical to a
LodgingReservation <https://schema.org/LodgingReservation> and so the first
question:

*Should we extend ReservationStatusType
<https://schema.org/ReservationStatusType> to have an extra enum value of
ReservationSearch or should we create a new Intangible call LodgingSearch
(or a better name)?*


*Common properties:*

   - checkinTime
   - checkoutTime
   - numAdults
   - numChildren
   - priceCurrency
   - totalPrice

*Additional properties*

   - numRooms : Integer or QuantitativeValue
   - childAge : Integer or QuantitativeValue


Any advice would be much appreciated

Thanks

Dan