I'll take the PS first..... I'll answer you in English since your English is definitely better than my French :)
As far as the answers to your questions, some additional information that you should provide is regarding the new sites, what exactly are the high risks? Are the risks in equipment theft? information theft? risky connectivity? etc...
As far as utilizing a terminal client vs. a thinclient vs. full client, you yourself need to answer this question based upon the information you have available.
To answer your questions (and I'm sure others will add even more information to my answers), here goes:
1. What are the risks?
With each system you have certain risks.
Thick client solution, you have local data storage/backup/reliability, information sharing, possibly user training issues. Also, support becomes a larger issue when you need to coordinate software/hardware upgrades across various locations to ensure that you maintain full compatibility.
Remote client solution, you eliminate all of the distributed information issues and most of the support issues, however, you now require a much more sophisticated server configuration, increase the risk of loss productivity due to network/internet outages, and risk the total loss of all productivity in the case of your server(s) going down for any reason.
2. Are you going the right way?
For your new/remote sites, my gut feeling is that utilizing terminal clients will be the best solution for you (as long as your internet is relatively reliable). As the level of technical know-how/support at the new sites is not stated, I will assume worst-case situation that the support there is very limited. In this case, it is relatively simple to preconfigure all of the equipment, ship it to the site, and have one of your techs fly in and perform the installation and provide basic instruction in how to connect new stations/troubleshoot problems.
3. The network traffic from the new sites to the central site will be significant, however, I would not go so far as to say it would be huge. Most terminal clients are designed to be run over slower circuits (<64k bandwidth), and with only five clients, having at least 128kb (preferred 256kb) should be more than enough. The largest issue would be if you start to print out documents to the remote sites, as that could possibly clog a low speed link for quite some time. Make sure the printers are configured as IP printers.
4. Web based solution? Hundreds, thousands, millions of web based solutions are out there, however, without knowing what solutions you actually need, it is impossible to say.
5. What should you think about?
The most important to think about is, how long can these remote sites be "offline" before you start experiencing significant financial impact to your company? If this is low, than you are fine, if this is high, than you need to consider how to keep the clients working regardless of which method you ultimately use.
6. Should you move everyone to winterm?
Evaluate it. How do your people work? Would it be economical? You already have 15 people/PCs working independently, would it be worth the money invested to purchase a new winterm server for them? I would not really consider this until you have the remote clients set up (to show how well it works), than (if feasible), migrate to winterm as you start having to replace the computers at your central site.