That approach isn't recommended, since the bus may skip messages between the time it is started and when the consumers are connected. Consumers connected to the bus endpoint also do not create subscriptions in the broker, so published messages won't be routed to the consumer.
You can use the host.ConnectReceiveEndpoint() to create a receive endpoint after the bus is started. The handle returned should be used to stop that receive endpoint before stopping the bus.
For request/response scenarios, or publishing messages only, the bus can be used without any additional queues as the temporary queue is designed for that purpose.