How to raise an RDP server (1C) with little bloodshed?

Question

1C

It is necessary to raise a server to which employees would connect remotely via RDP in order to work in 1C (UT) and Office. The company is a start-up, so at first the costs need to be minimized. As far as I understand, this can be done in three ways:
A. Place a physical server somewhere, roll Win Server, 1S, Office onto it.
You need a place for hardware, hardware, a connection with a white IP, software, admin. Everything seems to be clear.
Expensive, convenient, but, most likely, if it is relevant, then only after confirming the viability of the project.
B. Buy "cloud 1C" services such as
SAAS with all the consequences, big questions with custom configurations, strong dependence on the service. Do not want.
Q. Rent somewhere VPS\VDS with Win Server under 1C\Office? Looks attractive.
Questions:
1. Since. a startup is supposed, the management is considering the possibility of installing 1C on VPS \ VDS without a license (at the initial stage). How will the provider react to this? I don't think he will like it.
2. If the startup shoots, you will need to install licensed 1s. She has an iron HASP key. How to use it in case of VPS\VDS?
3. Where is the best place to look?
2. In the case of VPS \ VDS, how to protect yourself from bad things (except for backups)? Those. provide secure employee access + malware protection? It is clear that the topic is vast, but I would like to hear a summary of what is worth doing, or a link where it is correctly written for noobs.
Thank you.
=====
Because the question was asked initially in order to delve into the nuances of a variety of approaches in all their diversity, marked everyone with answers, tk. they were all useful to me and will allow me to make the best, as it seems to me, choice - and, if necessary, quickly change it :)