Not calling it a bug yet.
Prerequisite to #2451657: Views should not condition joins on the langcode of fields that are not translatable
1. Create a new integer field on the first one,
2. Reuse the field on the second content type.
3. Export the configuration of both fields
The first has:
translatable: true
The second has:
translatable: false