If there’s a predetermined set of feature names, then you could translate them using static message translations.
{% for row in entry.myTableField %}
<dt>{{ row.featureName|t }}</dt>
<dd>{{ row.featureValue }}</dd>
{% endfor %}
If new products will always be introducing new feature names, then that might become impractical, as you’d be constantsly adding new values to your translation file.
You could set up a custom translation message source + category in config/app.php
that pulls translations in from a separate, translatable Table field on a Global Set, for instance, but that could be overkill.
The other option is to use Verbb’s Super Table plugin, which will let you mark certain fields as translatable.