I don't have the means to test anything other than the actual application service deployment but I was able to prevent the front end virtual servers and pools at ports 448 and 5080 from being created by editing the template using the BIG-IP GUI and commenting out the lines of code as follows:
Scroll down until you find the first reference for " create pool 4" and comment out the three lines that appear below it by placing a " " in front of each line. Your result should look similar to this:
create pool 4
set members_action [build_pool_members $servers $lb_method $port_4]
set pool_name_4 [format "%s_%s_%s" $tmsh::app_name $part_name_4 pool]
tmsh_create "/ ltm pool" "$pool_name_4 $members_action monitor $monitor_name load-balancing-mode $lb_method service-down-action reset"
Scroll down and find the first reference for " create pool 14" and comment out the three lines that appear below it (same as above).
Scroll down to find the first reference for " create VS 4" and comment out the 4 lines that appear below it. Your result should look similar to this:
create VS 4
set vs_name [format "%s_%s" $tmsh::app_name $part_name_4]
set destination [create_safe_destination $::front_end_ip__addr $port_4]
tmsh_create "/ ltm virtual" "$vs_name destination $destination $snat_action $mask_action pool $pool_name_4 profiles none persist replace-all-with \{ $saa_persist_profile_name \} $vlan_action"
add_client_server_profiles $vs_name $tcp_profile_name $tcp_profile_name
Scroll down to find the first reference for " create VS 14" and comment out the 4 lines that appear below it (same as above).
You'll have to test the finished configuration to make sure it does what you expect it to. Hope it works!