Maybe it does not help with v4.0 for this specific problem with importing chords.

If v3.0 allows for using an optional textstring as a chord specifier rather than the detailed <kind> chord specifier as it seems to be at the moment (see above). Then maybe this problem will remain in 4.0 unless BIAB changes the way to interpret the chord specifier (only a speculation).