Tweening does smooth things out if your logic is running at a relatively low speed. However, what I would ask is why would you want to update your game at 10 updates per second in the first place? Even 8 bit computers managed more than that!
Basically, the higher the updates per second you use, the less need there is for additional tweening. If your game logic has so much work to do that 200 times per second is not feasible, then introduce some tweening as well to help matters along visually.
Having said that, tweening is a little more advanced that straight forward fixed rate logic, so as you're only just getting to grips with this timing business, I would recommend you start with the simplest version first, and then try to include tweening into your projects at a later date - if you find a need to actually use it.
Basically, the higher the updates per second you use, the less need there is for additional tweening. If your game logic has so much work to do that 200 times per second is not feasible, then introduce some tweening as well to help matters along visually.
Having said that, tweening is a little more advanced that straight forward fixed rate logic, so as you're only just getting to grips with this timing business, I would recommend you start with the simplest version first, and then try to include tweening into your projects at a later date - if you find a need to actually use it.