If I had to guess, I would say you could. I think even in community classic we were able to manually put in those <li-asdf> tags into the message body, and as long as it resolved to an actual object and ID, it would work.
Aurora uses GraphQL for 100% of its interactions with the DB/Backend, and I'm quite certain we save those tags to the DB.
So, what you can do for any Aurora operation, is "do the thing" with brower dev tools network tab open. You may need to make sure to "preserve log" in case the page reloads. You will see a "graphql?opname=Something" in the requests. If you look at the payload of that request, you can see the data they are sending to graphql.
The "opname" you see in the network requests just map to a .query.graphql (or .mutation.graphql) on the backend, with relevant variables set. So only sort of gotcha with this is it may not be immediately obvious which graphql query or mutations they are using,