Partial workaround

Now you can use a custom template by adding the following code in the "Initialization JavaScript Function" attribute on every page item that use a specific LOV.

function(options) {
options.display = "list";
options.recordTemplate = (
'<li data-id="&' + 'DRIVER_ID' + '." class="u-flex u-align-items-center u-justify-content-stretch">'
  + '<span class="fa fa-user t-Avatar t-Avatar--initials t-Avatar--sm u-color margin-right-sm"></span>'
  + '<div class="u-flex-grow-1">'
   + '&' + 'DRIVER_NAME' + '.'
   + '<div class="detail">'
    + '<span class="t-Badge-icon fa fa-shield u-pullLeft margin-right-sm" aria-hidden="true"></span>'
    + '&' + 'TEAM_NAME' + '.'
   + '</div>'
  + '</div>'
  + '<div class="margin-left-sm">'
   + '<span class="t-Badge t-Badge--success t-Badge--subtle  " role="status" aria-label="Role Admin" title="Role Admin">'
    + '<span class="t-Badge-icon fa fa-hashtag" aria-hidden="true"></span>'
    + '<span class="t-Badge-value">&' + 'DRIVER_NUMBER' + '.</span>'
   + '</span>'
  + '</div>'
 + '</li>'
);
return options;
}

As you can see, this solution isn't exactly ideal because uses a strange syntax to map the columns and because the code has to be repeated in each item.

The ideal would be to be able to define the template directly in the shared components of the app, in the properties of the list.