Will that limitation be lifted at some point?

Yes, we plan to remove this constraint, even if it could cause errors on the call sites when typealiasing an expect class to a java class: https://youtrack.jetbrains.com/issue/KT-22237#focus=streamItem-27-3181354.0-0

Oh, that's fine, we're already used to named arguments being broken with typealiasing 🙂

throw RuntimeException(message = "")

e:
None of the following functions can be called with the arguments supplied: 
public final fun <init>(): kotlin.RuntimeException /* = java.lang.RuntimeException */ defined in kotlin.RuntimeException
public final fun <init>(p0: String!): kotlin.RuntimeException /* = java.lang.RuntimeException */ defined in kotlin.RuntimeException
public final fun <init>(p0: String!, p1: Throwable!): kotlin.RuntimeException /* = java.lang.RuntimeException */ defined in kotlin.RuntimeException
public final fun <init>(p0: String!, p1: Throwable!, p2: Boolean, p3: Boolean): kotlin.RuntimeException /* = java.lang.RuntimeException */ defined in kotlin.RuntimeException
public final fun <init>(p0: Throwable!): kotlin.RuntimeException /* = java.lang.RuntimeException */ defined in kotlin.RuntimeException