3819109 - New Concur Travel - Why can a user without Request User permission book Travel, but doesn't have Request generated?

We noticed a change in behavior between legacy Concur Travel and new Concur Travel.
In legacy, there's a blocking warning message in the Hotel tab, making it impossible for the delegate without Request user permission to make a booking  This is expected behavior for Legacy Concur Travel with Request integration - Request User permission is needed for both end user and their delegate for the process to work as expected. This behavior is also present when the end user does not have the Request User permission.

On the other hand, in New Concur Travel this restriction was lifted and it is now possible for the delegate to make a booking on behalf of the user even without the Request User permission e.g. flight, car

However, it is equally possible for an end user who is missing Request User permission to make a booking but without any request being generated. Why?

New Concur Travel currently allows users or delegates without Request User permission to make bookings without generating a Request — a known feature gap compared with legacy Concur that is planned to be addressed. , KBA , CON-REQ-REQ , Request , Problem